Merge pull request #2186 from urfave/make-v3-recommended

Document that `v3` series is recommended for new development

Author: meatballhat

docs/index.md

@@ -46,10 +46,12 @@ Go Modules are required when using this package. [See the go blog guide on using
 
 ### Using `v3` releases
 
-The latest `v3` release may be installed via the `/v3` suffix. The state of the [`main`
-branch](https://github.com/urfave/cli/tree/main) at any given time may correspond to a
-`v3` series release or pre-release.  Please see the [`v3` migration
-guide](./migrate-v2-to-v3.md) on using v3 if you are upgrading from v2.
+The latest `v3` release may be installed via the `/v3` suffix and is the
+recommended version for all new development. The state of the [`main`
+branch](https://github.com/urfave/cli/tree/main) at any given time **may**
+correspond to a `v3` series release or pre-release.  Please see the [`v3`
+migration guide](./migrate-v2-to-v3.md) on using v3 if you are upgrading from
+v2.
 
 ```sh
 go get github.com/urfave/cli/v3@latest
@@ -63,10 +65,11 @@ import (
 
 ### Using `v2` releases
 
-The `v2` series is the recommended version for new development. Ongoing
-maintenance is done on the [`v2-maint`
-branch](https://github.com/urfave/cli/tree/v2-maint) which receives **minor**
-improvements, bug fixes, and security fixes.
+:warning: The `v2` series is receiving **security and bug fixes only** via the
+[`v2-maint` branch](https://github.com/urfave/cli/tree/v2-maint) and **should
+not** be used in new development. Please see the [`v3` migration
+guide](./migrate-v2-to-v3.md) and feel free to open an issue or discussion if
+you need help with the migration to `v3`.
 
 ```sh
 go get github.com/urfave/cli/v2@latest
@@ -81,7 +84,7 @@ import (
 ### Using `v1` releases
 
 :warning: The `v1` series is receiving **security fixes only** via the
-[`v1-maint`](https://github.com/urfave/cli/tree/v1-maint) branch and **should
+[`v1-maint` branch](https://github.com/urfave/cli/tree/v1-maint) and **should
 not** be used in new development. Please see the [`v2` migration
 guide](./migrate-v1-to-v2.md) and feel free to open an issue or discussion if
 you need help with the migration to `v2`.