Relocates and expands table.

Author: szabosteve

docs/contribute/_snippets/tag-processing.md

@@ -2,34 +2,25 @@
 
 Specifically for versioned products, badges will display differently when the `applies_to` key specifies a product version that has not been released to our customers yet.
 
-* `Planned` (if the lifecycle is preview, beta, or ga)
-  
-  Example: {applies_to}`stack: ga 99.99`
-* `Deprecation planned` (if the lifecycle is deprecated)
-  
-  Example: {applies_to}`stack: deprecated 99.99`
-* `Removal planned` (if the lifecycle is removed)
-
-  Example: {applies_to}`stack: removed 99.99`
-
-This is computed at build time (there is a docs build every 30 minutes). The documentation team tracks and maintains released versions for these products centrally in [`versions.yml`](https://github.com/elastic/docs-builder/blob/main/config/versions.yml). 
-When multiple lifecycle statuses and versions are specified in the sources, several badges are shown.
-
-:::{note}
-Visuals and wording in the output documentation are subject to changes and optimizations.
-:::
-
-The following table shows how the badge text and corresponding tooltip text vary by release status for each lifecycle value. Hoover over the example badges for tooltip text.
+The following table shows how badges for versioned products are displayed based on the release status for each lifecycle value. Hover over the example badges for the tooltip text.
 
 | Lifecycle   | Release status | Badge text                                                                        |
 |-------------|----------------|-----------------------------------------------------------------------------------|
-| preview     | prerelease     | Planned                                                                           |
+| preview     | prerelease     | {applies_to}`stack: preview 99.99`                                                |
 |             | post-release   | `<KEY> PREVIEW <VERSION>` <br><br> example: {applies_to}`stack: preview 9.1`      |
-| beta        | prerelease     | Planned                                                                           |
+| beta        | prerelease     | {applies_to}`stack: beta 99.99`                                                   |
 |             | post-release   | `<KEY> BETA <VERSION>` <br><br> example: {applies_to}`stack: beta 9.1`            |
-| ga          | prerelease     | Planned                                                                           |
+| ga          | prerelease     | {applies_to}`stack: ga 99.99`                                                     |
 |             | post-release   | `<KEY> <VERSION>` <br><br> example: {applies_to}`stack: ga 9.1`                   |
-| deprecated  | prerelease     | Deprecation planned                                                               |
+| deprecated  | prerelease     | {applies_to}`stack: deprecated 99.99`                                             |
 |             | post-release   | `<KEY> DEPRECATED <VERSION>` <br><br> example: {applies_to}`stack: deprecated 9.1`|
-| removed     | prerelease     | Removal planned                                                                   |
+| removed     | prerelease     | {applies_to}`stack: removed 99.99`                                                |
 |             | post-release   | `<KEY> REMOVED <VERSION>` <br><br> example: {applies_to}`stack: removed 9.1`      |
+
+This is computed at build time (there is a docs build every 30 minutes). The documentation team tracks and maintains released versions for these products centrally in [`versions.yml`](https://github.com/elastic/docs-builder/blob/main/config/versions.yml).
+
+When multiple lifecycle statuses and versions are specified in the sources, several badges are shown.
+
+:::{note}
+Visuals and wording in the output documentation are subject to changes and optimizations.
+:::