Apply suggestions from code review

Co-authored-by: Jeff Matthews <matthews.jeffery@gmail.com>

Author: sirugh

src/content/docs/setup/configuration/content-delivery-network.mdx

@@ -685,11 +685,11 @@ Ensure that the base URL change is propagated to Catalog Service. You can do thi
 Fastly VCL and CDN configuration can be a bit overwhelming at first. Here's a collection of troubleshooting steps that might help you if you have problems.
 </Aside>
 
-### Fastly API Quick Reference
+### Fastly API quick reference
 
 With your Fastly API Token you can make requests against the Fastly API for information or data that may be otherwise inaccessible. You can find your API Token in your Commerce Admin view under **Stores** > **Settings** > **Configuration** > **Advanced** > **System** > **Full Page Cache** > **Fastly Configuration**.
 
-Here's a quick reference of things you can do with your API Token. More details can be found on [Fastly's API docs](https://www.fastly.com/documentation/reference/api/).
+Here's a quick reference of things you can do with your API Token. See [Fastly's API documentation](https://www.fastly.com/documentation/reference/api/) for more details.
 
 ```bash
 # retrieve active version
@@ -702,13 +702,13 @@ curl -H "Fastly-Key: API_TOKEN" "https://api.fastly.com/service/SERVICE_ID/versi
 curl -H "Fastly-Key: API_TOKEN" "https://api.fastly.com/service/SERVICE_ID/version/VERSION/snippet"
 ```
 
-### Missing Snippets
+### Missing snippets
 
-Fastly maintains a "version" of your snippets remotely on their servers. These versions are never pulled "down" to your Commerce Environment, but can be "pushed" from your environment to Fastly. Unintentional local changes can therefore cause things to become out of sync.
+Fastly maintains a "version" of your snippets remotely on their servers. These versions are never pulled "down" to your Commerce environment, but can be "pushed" from your environment to Fastly. Unintentional local changes can cause things to become out of sync.
 
-For example, renaming a snippet actually creates a new snippet with the new name, and does not delete the old one. Thus you should not rename snippets unless you must. See [this issue](https://github.com/fastly/fastly-magento2/issues/708) for more information.
+For example, renaming a snippet actually creates a new snippet with the new name, and does not delete the old one. You should not rename snippets unless you must. See [this issue](https://github.com/fastly/fastly-magento2/issues/708) for more information.
 
-Another issue is that custom VCL snippets are kept on your environment in `var/vcl_snippets_custom/`. If that folder or contents are deleted, then you will be unable to view, edit, or modify the snippets even though they remain active in Fastly.
+Your environment stores custom VCL snippets in the `var/vcl_snippets_custom/` directory. If you delete that directory or its contents, you will not be able to view, edit, or modify the snippets, even though they remain active in Fastly."
 
 To resolve this, you should use the Fastly API to "pull" all snippets and then place them back in that folder (with permission **775**). The following table details how to construct the file correctly: