Update instance-audiences.mdx

Author: chdeskur

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

@@ -117,20 +117,6 @@ products:
     slug: getting-started
     subtitle: Introduction to Plant Store
     # No audience defined - included in all instances
-
-versions:
-  - display-name: v3
-    path: ./versions/v3.yml
-    audiences:
-      - public
-  - display-name: v2
-    path: ./versions/v2.yml
-    audiences:
-      - public
-  - display-name: v1 (Internal Only)
-    path: ./versions/v1.yml
-    audiences:
-      - internal
 ```
 </CodeBlock>
 
@@ -139,12 +125,10 @@ In this example:
 - The public instance at `docs.plantstore.com` will include:
   - Plant API product (matches `public` audience)
   - Getting Started product (no audience defined)
-  - v3 and v2 versions (match `public` audience)
 
 - The internal instance at `internal.plantstore.docs.buildwithfern.com` will include:
   - Admin API product (matches `internal` audience)
   - Getting Started product (no audience defined)
-  - v1 version (matches `internal` audience)
 
 ## Publishing to specific instances
 
@@ -165,4 +149,4 @@ Instance audiences work alongside [API Reference audiences](/docs/api-references
 - **Instance audiences** - Control which products and versions appear in each instance
 - **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. Within those products, the API Reference should be marked as `public` so it is filtered to show only `public` endpoints.