198c9b8daecc44fbda6a6494c566c723920f030a lrnassar Wed Mar 11 18:25:21 2026 -0700 Fixing a few hundred clear typos with the help of Claude. Some are less important in code comments, but majority of them are in user-facing places. I manually approved 60%+ of the changes and didn't see any that were an incorrect suggestion, at worst it was potentially uncessesary, like a code comment having cant instead of can't. No RM. diff --git src/hg/htdocs/goldenPath/help/api.html src/hg/htdocs/goldenPath/help/api.html index 1ec2de5f222..2c64baf8e5e 100755 --- src/hg/htdocs/goldenPath/help/api.html +++ src/hg/htdocs/goldenPath/help/api.html @@ -52,31 +52,31 @@ </ul> <p> All these options offer faster bulk downloads and are often easier to parse from scripting languages. If, however, you write Javascript clients or need only a few features within a given range, then the endpoints documented on this page may address your needs. If you require an option or endpoint not listed below for your specific use case, <a href="/contacts.html" target="_blank">contact us</a> and we can try and implement the feature. </p> <h3>Conditions of use</h3> <ul> <li> Avoid excessive or heavy queries that may impact the server performance. Inappropriate query use will result in a restriction of access. </li> <li> We generally recommend a maximum of one hit every second, but there is no strict limit on queries - using the API. A botDelay system is in place to avoid overloads onto the system. + using the API. A botDelay system is in place to avoid overloads on the system. <li> If you begin to notice a significant delay between requests, adjust your code or try an alternative method to retrieve our data. </li> </ul> <p> For more details about the Conditions of Use, please refer to the following page, <a href="/conditions.html" target="_blank">Genome Browser Conditions of Use</a>. If you plan to execute a query that you think may be excessive, <a href="/contacts.html" target="_blank">contact UCSC</a> first to avoid the possibility of temporarily restricting your access to the REST API. </p> <!-- ========== What is REST? ============================== --> <a id="REST"></a> @@ -153,31 +153,31 @@ genome</li> <li><b>/getData/sequence</b> - return sequence from specified hub or database genome</li> <li><b>/getData/track</b> - return data from specified track in hub or database genome</li> <li><b>/search</b> - return search matches within a UCSC Genome Browser genome assembly</li> </ul> </p> <!-- ========== Parameters to endpoint functions ======================= --> <a id="Parameters"></a> <h2>Parameters to endpoint functions</h2> <p> <ul> <li>maxItemsOutput=1000000 - limit number of items to output, default: 1,000,000, maximum limit: 1,000,000 (use <em>-1</em> to get maximum output)</li> <li>hubUrl=<url> - specify track hub or assembly hub URL</li> -<li>genome=<name> - specify genome assembly in UCSC Genome Browser or track/assembly hub. Use with with /list/genarkGenomes to test for existence.</li> +<li>genome=<name> - specify genome assembly in UCSC Genome Browser or track/assembly hub. Use with /list/genarkGenomes to test for existence.</li> <li>track=<trackName> - specify data track in track/assembly hub or UCSC database genome assembly</li> <li>chrom=<chrN> - specify chromosome name for sequence or track data</li> <li>start=<123> - specify start coordinate (0 relative) for data from track or sequence retrieval (start and end required together). See also: <a href='https://genome-blog.gi.ucsc.edu/blog/the-ucsc-genome-browser-coordinate-counting-systems/' target=_blank>UCSC browser coordinate counting systems</a></li> <li>end=<456> - specify end coordinate (1 relative) for data from track or sequence retrieval (start and end required together). See also: <a href='https://genome-blog.gi.ucsc.edu/blog/the-ucsc-genome-browser-coordinate-counting-systems/' target=_blank>UCSC browser coordinate counting systems</a></li> <li>q=<search word(s)> - used with <em>/findGenome</em>, a search string</li> <li>browser=<mustExist|mayExist|notExist> - used with <em>/findGenome</em>, <em>mustExist</em> result only for assemblies in the UCSC browser, <em>mayExist</em> may exist in the UCSC browser, or may not, <em>notExist</em> not yet available in the browser. default is <em>mustExist</em> </li> <li>statsOnly=1 - on <em>/findGenome</em> function, only show statistics about search result</li> <li>year=<2025> - on <em>/findGenome</em> function, only show search result for given year, default is any year</li>