copyedits

Author: ethanpalm

navigation.mdx

@@ -4,9 +4,9 @@ description: "Structure and customize your documentation's navigation hierarchy"
 icon: "map"
 ---
 
-The [navigation](settings#param-navigation) property in `docs.json` defines how your documentation is organized.
+The [navigation](settings#param-navigation) property in `docs.json` controls the structure and information hierarchy of your documentation.
 
-With proper navigation configuration, you can organize your content into a logical hierarchy that makes it easy for users to find exactly what they're looking for.
+With proper navigation configuration, you can organize your content so that users can find exactly what they're looking for.
 
 <Info>
   Do not use `api` or `mcp` as titles for any navigation element. The `/api` and `/mcp` paths are reserved in production and will cause pages to return 404 errors if their URLs contain `/api` or `/mcp`.
@@ -238,9 +238,9 @@ In the `navigation` object, `anchors` is an array where each entry is an object
 }
 ```
 
-Use a `global` object for anchors to external links that exist outside your navigation hierarchy. Anchors in a `global` object are particularly useful for linking to resources that are not part of your documentation like a blog or support portal, but should be readily accessible to your users.
+For anchors that direct to external links only, use the `global` keyword. Anchors in a `global` object must have an `href` field and cannot point to a relative path. 
 
-Anchors in a `global` object must have an `href` field and cannot direct to a relative path.
+Global anchors are particularly useful for linking to resources that are not part of your documentation, but should be readily accessible to your users like a blog or support portal
 
 ```json
 {