<?xml version="1.0" encoding="utf-8"?>
<Spec id="53" path="\2\a\2abc19580b6ea5dfd9256a9e94b07010.pdf"><Text id="5138" page="1">formulation and publication of API publications is not intended in any way to inhibit anyone from using any other practices.</Text><Text id="5139" page="1">Neither API nor any of API&apos;s employees, subcontractors, consultants, committees, or other assignees make any warranty or representation, either express or implied, with respect to the accuracy, completeness, or usefulness of the information contained herein, or assumeanyliability or responsibility for any use, or the results of such use, of any information or process disclosed in this publication. Neither API nor any of API&apos;s employees, subcontractors, consultants, or other assignees represent that use of this publication would not infringe upon privately owned rights.</Text><Text id="5335" page="1">API publications may be used by anyone desiring to do so. Every effort has been made by the Institute to assure the accuracy and reliability of the data contained in them; however, the Institute makes no representation,</Text><Text id="5336" page="1">API publications may be used by anyone desiring to do so. Every effort has been made by the Institute to assure the accuracy and reliability of the data contained in them; however, the Institute makes no representation,</Text><Text id="5337" page="1">API publications are published to facilitate the broad availability of proven, sound engineering and operating practices. These publications are not intended to obviate the need for applying sound engineering judgment</Text></Spec>