Copyedit customization pages

Author: ethanpalm

api-playground/customization/adding-sdk-examples.mdx

@@ -3,7 +3,7 @@ title: "Adding SDK examples"
 description: "Display language-specific code samples alongside your API endpoints to show developers how to use your SDKs"
 ---
 
-If your users interact with your API using an SDK rather than directly through a network request, you can use the `x-codeSamples` extension to add code samples to your OpenAPI document and Mintlify will display them in your OpenAPI pages.
+If your users interact with your API using an SDK rather than directly through a network request, you can use the `x-codeSamples` extension to add code samples to your OpenAPI document and display them in your OpenAPI pages.
 
 This property can be added to any request method and has the following schema.
 
@@ -19,7 +19,7 @@ This property can be added to any request method and has the following schema.
   The source code of the sample.
 </ParamField>
 
-Here is an example of some code samples for a plant tracking app, which has both a Bash CLI tool and a JavaScript SDK.
+Here is an example of code samples for a plant tracking app, which has both a Bash CLI tool and a JavaScript SDK.
 
 ```yaml
 paths:

api-playground/customization/complex-data-types.mdx

@@ -3,25 +3,25 @@ title: "Complex data types"
 description: "Describe APIs with flexible schemas, optional properties, and multiple data formats using `oneOf`, `anyOf`, and `allOf` keywords"
 ---
 
-When your API accepts multiple data formats, has conditional fields, or uses inheritance patterns, OpenAPI's schema composition keywords help you document these flexible structures clearly. Using `oneOf`, `anyOf`, and `allOf`, you can describe APIs that handle different input types or combine multiple schemas into comprehensive data models.
+When your API accepts multiple data formats, has conditional fields, or uses inheritance patterns, OpenAPI's schema composition keywords help you document these flexible structures. Using `oneOf`, `anyOf`, and `allOf`, you can describe APIs that handle different input types or combine multiple schemas into comprehensive data models.
 
 ## `oneOf`, `anyOf`, `allOf` keywords
 
 For complex data types, OpenAPI provides keywords for combining schemas:
 
-- `allOf`: Combines multiple schemas (like merging objects or extending a base schema). Functions like an *and* operator. 
-- `anyOf`: Accepts data matching any of the provided schemas. Functions like an *or* operator.
-- `oneOf`: Accepts data matching exactly one of the provided schemas. Functions like an *exclusive-or* operator.
+- `allOf`: Combines multiple schemas (like merging objects or extending a base schema). Functions like an `and` operator. 
+- `anyOf`: Accepts data matching any of the provided schemas. Functions like an `or` operator.
+- `oneOf`: Accepts data matching exactly one of the provided schemas. Functions like an `exclusive-or` operator.
 
-<Warning>Mintlify treats `oneOf` and `anyOf` identically. Most APIs work fine with `anyOf` since the practical difference is rarely important to users.</Warning>
+<Warning>Mintlify treats `oneOf` and `anyOf` identically since the practical difference rarely affects using the API.</Warning>
 
 For detailed specifications of these keywords see the [OpenAPI documentation](https://swagger.io/docs/specification/data-models/oneof-anyof-allof-not/).
 
-<Info>The `not` keyword is not currently supported.</Info>
+<Info>The `not` keyword is currently unsupported.</Info>
 
 ### Combining schemas with `allOf`
 
-When you use `allOf`, Mintlify performs some preprocessing on your OpenAPI document to display complex combinations in a readable way. For example, when you combine two object schemas with `allOf`, Mintlify combines the properties of both into a single object. This becomes especially useful when leveraging OpenAPI's [reusable `components`](https://swagger.io/docs/specification/components/).
+When you use `allOf`, Mintlify performs some preprocessing on your OpenAPI document to display complex combinations in a readable way. For example, when you combine two object schemas with `allOf`, Mintlify combines the properties of both into a single object. This becomes especially useful when leveraging OpenAPI's reusable [`components`](https://swagger.io/docs/specification/components/).
 
 ```yaml
 org_with_users:

api-playground/customization/managing-page-visibility.mdx

@@ -3,10 +3,9 @@ title: "Managing page visibility"
 description: "Control which endpoints from your OpenAPI specification appear in your documentation navigation"
 ---
 
+You can control which OpenAPI operations get published as documentation pages and their visibility in navigation. This is useful for internal-only endpoints, deprecated operations, beta features, or endpoints that should be accessible via direct URL but not discoverable through site navigation.
 
-You can control exactly which parts of your OpenAPI specification get published and how they're organized. Hiding pages can be useful when you're documenting internal APIs, beta features, or other endpoints that shouldn't appear in navigation.
-
-If your pages are autogenerated from an OpenAPI document, you can control which endpoints get published and how they appear in your documentation with the `x-hidden` and `x-excluded` extensions.
+If your pages are autogenerated from an OpenAPI document, you can manage page visibility with the `x-hidden` and `x-excluded` extensions.
 
 ## `x-hidden`