improve docs

Author: 1cg

www/content/_index.md

@@ -91,8 +91,9 @@ if(window.location.search=="?ads=true") {
 </div>
 
 <div class="alert">
-<b>NEWS:</b> htmx 2.0 has been released!  It is not currently marked as <code>latest</code> in NPM so that people using 
-the <a href="https://v1.htmx.org">1.x line</a> are not accidentally upgraded.  We will mark 2.0 as <code>latest</code> at some point in 2025.
+<b>NEWS:</b> htmx 2.0 has been released!  It is not currently marked as [<code>latest</code>](https://docs.npmjs.com/cli/v10/commands/npm-dist-tag#purpose) 
+in NPM so that people using the <a href="https://v1.htmx.org">1.x line</a> are not accidentally upgraded.  We will mark 
+2.0 as <code>latest</code> at some point in 2025.
 </div>
 
 <h2>introduction</h2>

www/content/posts/2024-06-17-htmx-2.0.0-is-released.md

@@ -10,9 +10,9 @@ tag = ["posts", "announcements"]
 I'm very happy to announce the release of htmx 2.0.  This release ends support for Internet Explorer and tightens up some
 defaults, but does not change most of the core functionality or the core API of the library.
 
-Note that we are not marking 2.0 as `current` in NPM because we do not want to force-upgrade users who are relying on 
-non-versioned URLs for htmx.  Instead, 1.x will remain `current` and the 2.0 line will remain `next` until Jan 1, 2025.
-The website, however, will reference 2.0.
+Note that we are not marking 2.0 as [`latest`](https://docs.npmjs.com/cli/v10/commands/npm-dist-tag#purpose) in NPM 
+because we do not want to force-upgrade users who are relying on non-versioned CDN URLs for htmx.  Instead, 1.x will
+remain `latest` and the 2.0 line will remain `next` until Jan 1, 2025. The website, however, will reference 2.0.
 
 ### Major Changes
 

www/themes/htmx-theme/static/css/site.css

@@ -69,7 +69,6 @@ table {
   border: 1px solid var(--alertBorder);
   margin: 24px 8px;
   padding: 12px;
-  border-radius: 8px;
   background-color: var(--alertBackground);
   filter: drop-shadow(3px 3px var(--alertShadow));
 }