layout + supported tweaks and clarifications

Author: NickJosevski

src/pages/docs/releases/channels/index.md

@@ -142,14 +142,26 @@ When **Use most recently published** is selected:
 
 2. Click **Save**.
 
-The **Design rule** dialog isn't available for Most recently published rules — there's no SemVer range to evaluate candidates against. The regex filter determines which candidates qualify; Octopus then picks the candidate with the latest publish date. When two candidates share the same publish timestamp (a rare tie), the SemVer-higher version wins as a deterministic secondary sort.
+The **Design rule** dialog isn't available for Most recently published rules — there's no SemVer range to evaluate candidates against. The regex filter determines which candidates qualify; Octopus then picks the candidate with the latest publish date. When two candidates share the same publish timestamp (a rare tie), the higher version wins as a deterministic secondary sort, using Octopus's numeric-aware version comparison rather than a plain alphabetical sort (so `build-10` sorts above `build-9`).
 
 :::div{.hint}
-**Feed support.** Most recently published ordering needs the feed to report a publish date per version. It is supported on the built-in NuGet feed, external HTTP and filesystem NuGet feeds, Amazon S3, Google Cloud Storage, Helm, NPM, PyPI, and Artifactory Generic feeds. 
+**Feed support.** Most recently published ordering needs the feed to report a publish date per version.
 
-It is **not** supported on container or OCI registry feeds (Docker, DockerHub, GitHub Container Registry, Amazon ECR, Google GCR, or any OCI registry) because their tag-listing APIs return tag names only — fetching per-tag dates would require an extra manifest call for every tag. When you choose Most recently published for a step that targets one of these feeds, the channel rule editor warns you.
-
-Other feeds that don't report a publish date — including Maven and GitHub feeds — don't error, but they can't order by publish date either: they silently fall back to version-string ordering. Only use Most recently published with the feed types listed above.
+| Feed | Most recently published | Notes |
+| --- | --- | --- |
+| Built-in NuGet | Supported | |
+| External NuGet (HTTP and filesystem) | Supported | |
+| Amazon S3 | Supported | |
+| Google Cloud Storage | Supported | |
+| Helm | Supported | |
+| NPM | Supported | |
+| PyPI | Supported | |
+| Artifactory Generic | Supported | |
+| Google Container Registry (GCR) and Google Artifact Registry (GAR) | Supported | Their tag-listing responses include per-tag publish dates, so ordering works automatically. |
+| Container / OCI registries — Docker, DockerHub, GitHub Container Registry, Amazon ECR, or any OCI registry | Not supported | Their tag-listing APIs return tag names only; fetching per-tag dates would require an extra manifest call for every tag. The channel rule editor warns you when you choose Most recently published for a step that targets one of these feeds. |
+| Maven, GitHub | Not supported (no error) | These feeds don't report a publish date, so they can't order by it — they silently fall back to version-string ordering. |
+
+Only use Most recently published with the feeds listed as supported above.
 :::
 
 ### Git protection rules {#git-protection-rules}