3da4d31d4cb64417945af1231cc1f2dc603123fb
jnavarr5
  Tue Feb 3 16:24:53 2026 -0800
Making minor edits to the news announcement for Hub Space, refs #36290

diff --git src/hg/htdocs/goldenPath/newsarch.html src/hg/htdocs/goldenPath/newsarch.html
index 7a91ee7eb7f..15af2794149 100755
--- src/hg/htdocs/goldenPath/newsarch.html
+++ src/hg/htdocs/goldenPath/newsarch.html
@@ -80,81 +80,81 @@
 whether that was Genes and Gene Predictions, Conservation, Variation, or any other group. Now, all
 your active tracks appear together in the <b>Visible Tracks</b> group, making it faster and easier
 to adjust display modes for visible tracks.
 </p>
 <p>
 The &quot;Visible Tracks&quot; group will appear only when more than 32 tracks are available for a
 genome assembly.
 </p>
 <p>
 We would like to thank Chris Lee and Jairo Navarro Gonzalez for releasing this feature.</p>
 
 <a name="020326b"></a>
 <h2>Feb. 03, 2026 &nbsp;&nbsp; Hub Space: Host Your Track Hubs Directly on the Genome Browser</h2>
 <p>
 We are excited to introduce <a href="/cgi-bin/hgHubConnect#hubUpload">Hub Space</a>, a new
-hosting service that allows users to upload and visualize track hub files directly on the UCSC
+hosting service that enables users to upload and visualize track hub files directly on the UCSC
 Genome Browser without relying on third-party hosting services such as Dropbox, Google Drive, or
 AWS.
 </p>
 
 <div class="text-center">
 <img src="/images/newsArchImages/HubSpace.png" width='65%'>
 </div>
 
 <p>
 <b>Hub Space Features:</b><br>
 Each account is allocated 10 GB of storage space. While we strive to maintain uninterrupted
 access, please maintain your own backups. Data persistence over the long term is not
 guaranteed. To request additional storage space, please
 <a href="/contacts.html">contact us</a>.
 </p>
 
 <p>
 <b>How to Use Hub Space:</b><br>
 There are two primary ways to upload your files:
 </p>
 
 <ol>
   <li>
     <b>Single file upload:</b> Upload individual binary-indexed files (bigBed, bigWig, BAM, VCF,
     and other supported formats) for immediate visualization.
   </li>
   <li>
-    <b>Complete hub upload:</b> Upload an entire track hub along with all supporting files
-    (hub.txt, bigWig, bigBed, etc.) to visualize the hub.
+    <b>Complete hub upload:</b> Upload the entire track hub, along with all supporting files
+    (hub.txt, bigWig, bigBed, etc.), to visualize the hub.
   </li>
 </ol>
 
 <p>
 If a hub.txt file is not provided when uploading data files, one is automatically generated.
 The generated hub.txt file is configured with the
 <a href="/goldenPath/help/trackDb/trackDbHub.html#useOneFile">useOneFile</a> trackDb setting, and
 as a result, each hub is limited to a single genome assembly. Editing the generated hub.txt file
 directly on the UCSC Genome Browser is not yet supported. To customize the hub configuration or
-data display, replace the generated hub.txt file with your own hub.txt file.
+data display, replace the generated hub.txt file with your own.
 </p>
 
 <p>
 To get started with Hub Space, visit the
 <a href="/cgi-bin/hgHubConnect#hubUpload">Track Data Hubs page</a> and
 click on the &quot;Hub Space&quot; tab. We would love to hear your feedback on this new feature.
 Please <a href="/contacts.html">contact us</a> and let us know what you think!
 </p>
 
 <p>
-We would like to thank Chris Lee and Jairo Navarro Gonzalez for the release of this feature.</p>
+We would like to thank Chris Lee and Jairo Navarro Gonzalez for releasing this feature.</p>
 
 <a name="011526"></a>
 <h2>Jan. 15, 2026 &nbsp;&nbsp; New ENCODE cCREs track available for human (hg38)</h2>
 <p>
 We are proud to announce a new <a href="/cgi-bin/hgTrackUi?db=hg38&c=chr7&g=cCREs&position=default"
         target="_blank">
 ENCODE Registry of cCREs (candidate Cis-Regulatory Elements)</a> 
 container track for the hg38/GRCh38 genome as described in <a target="_blank"
 href="https://www.nature.com/articles/s41586-025-09909-9">Moore et al., <em>Nature</em> 2026</a>. 
 This container contains candidate Cis-Regulatory 
 Elements (cCREs) generated by the ENCODE Consortium during Phase 4 (ENCODE4) and Phase 3 (ENCODE3).
 The previous "ENCODE3 cCREs" track is retained for archival purposes. The tracks include both integrated 
 (biosample-agnostic) and biosample-specific annotations derived from core epigenomic assays.</p>
 
 <div class="text-left">