Copilot edits

Author: ethanpalm

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

@@ -5,7 +5,7 @@ description: "Display language-specific code samples alongside your API endpoint
 
 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.
 
-This property can be added within any request method and has the following schema.
+This property can be added to any request method and has the following schema.
 
 <ParamField body="lang" type="string" required>
   The language of the code sample.

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

@@ -9,9 +9,9 @@ When your API accepts multiple data formats, has conditional fields, or uses inh
 
 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>
 
@@ -56,7 +56,7 @@ components:
 
 ### Providing options with `oneOf` and `anyOf`
 
-When you use `oneOf` or `anyOf`, Mintlify displays the options in a tabbed container. To give your options helpful names, specify a `title` field in each subschema. For example, here's how you might display two different types of delivery addresses:
+When you use `oneOf` or `anyOf`, Mintlify displays the options in a tabbed container. Specify a `title` field in each subschema to give your options names. For example, here's how you might display two different types of delivery addresses:
 
 ```yaml
 delivery_address:

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

@@ -10,7 +10,7 @@ If your pages are autogenerated from an OpenAPI document, you can control which
 
 ## `x-hidden`
 
-The `x-hidden` extension creates a page for an endpoint, but hides it from navigation. The page is only accessible by navigating directly its URL.
+The `x-hidden` extension creates a page for an endpoint, but hides it from navigation. The page is only accessible by navigating directly to its URL.
 
 Common use cases for `x-hidden` are:
 

api-playground/mdx/configuration.mdx

@@ -153,7 +153,7 @@ authMethod: "key"
 
 ### None
 
-The "none" authentication method is useful to disable authentication on a specific endpoint after setting a default in docs.json.
+The `none` authentication method is useful to disable authentication on a specific endpoint after setting a default in docs.json.
 
 <CodeGroup>
 ```md Page Metadata

api-playground/openapi-setup.mdx

@@ -12,7 +12,7 @@ To document your endpoints with OpenAPI, you need a valid OpenAPI document in ei
 
 ### Describing your API
 
-We reccomend the following resources to learn about and construct your OpenAPI documents.
+We recommend the following resources to learn about and construct your OpenAPI documents.
 
 - [Swagger's OpenAPI Guide](https://swagger.io/docs/specification/v3_0/basic-structure/) to learn the OpenAPI syntax.
 - [OpenAPI v3.1.0 Specification](https://github.com/OAI/OpenAPI-Specification/blob/main/versions/3.1.0.md) to reference details of the newest OpenAPI specification.