This change includes the following:

* Reordering the table of contents by updating the weight metadata in the `features.md` topic
* Adding a link to the Proto best practices topic from within `style.md`
* Updating the `version-support.md` topic with information about the 25.x release

PiperOrigin-RevId: 579176393
Change-Id: Ie5b115b7d2405e2bbf04a668168f37a99f387d47

Author: Protocol Buffer Team

content/editions/features.md

@@ -1,6 +1,6 @@
 +++
 title = "Feature Settings for Editions"
-weight = 42
+weight = 43
 description = "Protobuf Editions features and how they affect protobuf behavior."
 type = "docs"
 +++

content/programming-guides/style.md

@@ -98,11 +98,14 @@ enum FooBar {
 ```
 
 Each enum value should end with a semicolon, not a comma. Prefer prefixing enum
-values instead of surrounding them in an enclosing message. The zero value enum
-should have the suffix `UNSPECIFIED`, because a server or application that gets
-an unexpected enum value will mark the field as unset in the proto instance. The
-field accessor will then return the default value, which for enum fields is the
-first enum value.
+values instead of surrounding them in an enclosing message.
+
+The zero value enum should have the suffix `UNSPECIFIED`, because a server or
+application that gets an unexpected enum value will mark the field as unset in
+the proto instance. The field accessor will then return the default value, which
+for enum fields is the first enum value. For more information on the unspecified
+enum value, see
+[the Proto Best Practices page](/programming-guides/dos-donts#unspecified-enum).
 
 ## Services {#services}