Fix Vale style errors in instance audiences documentation

- Replace audience(s) with audiences for clarity
- Change 'does not' to 'doesn't' per Microsoft.Contractions
- Capitalize 'API Reference' per FernStyles.Reject
- Replace 'Latest/latest' version names with v3/v2 to avoid time-relative terms

Co-Authored-By: Catherine Deskur <[email protected]>

Author: devin-ai-integration[bot]

fern/products/docs/pages/navigation/instance-audiences.mdx

@@ -11,17 +11,17 @@ Instance audiences allow you to control which versions and products are included
 
 You can add audiences to three levels in your `docs.yml` configuration:
 
-1. **Instances** - Define which audience(s) an instance serves
-2. **Versions** - Tag versions with audience(s) they belong to
-3. **Products** - Tag products with audience(s) they belong to
+1. **Instances** - Define which audiences an instance serves
+2. **Versions** - Tag versions with audiences they belong to
+3. **Products** - Tag products with audiences they belong to
 
-When you add an audience to a product or version and it matches the audience of the instance, that content will be included. If the audience is defined but does not match the instance audience, it will be excluded. If no audience is defined, all content will be included by default.
+When you add an audience to a product or version and it matches the audience of the instance, that content will be included. If the audience is defined but doesn't match the instance audience, it will be excluded. If no audience is defined, all content will be included by default.
 
 ## Configuration
 
 ### Add audiences to instances
 
-Define which audience(s) an instance serves by adding the `audiences` property to an instance in your `docs.yml`:
+Define which audiences an instance serves by adding the `audiences` property to an instance in your `docs.yml`:
 
 <CodeBlock title="docs.yml">
 ```yaml {3-4}
@@ -42,12 +42,12 @@ Tag versions with audiences to control which instances include them:
 <CodeBlock title="docs.yml">
 ```yaml {4-5, 8-9}
 versions:
-  - display-name: Latest
-    path: ./versions/latest.yml
+  - display-name: v3
+    path: ./versions/v3.yml
     audiences:
       - public
-  - display-name: Beta
-    path: ./versions/beta.yml
+  - display-name: v2
+    path: ./versions/v2.yml
     audiences:
       - internal
       - beta
@@ -79,7 +79,7 @@ products:
 The filtering logic works as follows:
 
 - **Match**: If a version or product has an audience defined that matches the instance audience, it will be included
-- **No match**: If a version or product has an audience defined that does not match the instance audience, it will be excluded
+- **No match**: If a version or product has an audience defined that doesn't match the instance audience, it will be excluded
 - **No audience defined**: If no audience is defined on a version or product, it will be included in all instances
 
 ## Example configuration
@@ -158,11 +158,11 @@ fern docs publish --instance docs.plantstore.com
 fern docs publish --instance internal.plantstore.docs.buildwithfern.com
 ```
 
-## Combining with API reference audiences
+## Combining with API Reference audiences
 
-Instance audiences work alongside [API reference audiences](/docs/api-references/audiences), which filter endpoints and schemas within your API documentation. You can use both features together:
+Instance audiences work alongside [API Reference audiences](/docs/api-references/audiences), which filter endpoints and schemas within your API documentation. You can use both features together:
 
 - **Instance audiences** - Control which products and versions appear in each instance
-- **API reference audiences** - Control which endpoints and schemas appear within API references
+- **API Reference audiences** - Control which endpoints and schemas appear within API References
 
-For example, you might have a public instance that includes only public products, and within those products, the API references are further filtered to show only public endpoints.
+For example, you might have a public instance that includes only public products, and within those products, the API References are further filtered to show only public endpoints.