docs: misc improvements (#7107)

docs/local-api/outside-nextjs.mdx

@@ -2,7 +2,7 @@
 title: Using Payload outside Next.js
 label: Outside Next.js
 order: 20
-desc: Payload can be used outside of Next.js within standalone scripts or in other frameworks like Remix, Sveltekit, Nuxt, and similar. 
+desc: Payload can be used outside of Next.js within standalone scripts or in other frameworks like Remix, Sveltekit, Nuxt, and similar.
 keywords: local api, config, configuration, documentation, Content Management System, cms, headless, javascript, node, react, express
 ---
 
@@ -11,16 +11,16 @@ Payload can be used completely outside of Next.js which is helpful in cases like
 <Banner>
   <strong>Note:</strong>
   <br/>
-  Payload and all of its official packages are fully ESM. If you want to use Payload within your own projects, make sure you are writing your scripts in ESM format or dynamically importing the Payload config.
+  Payload and all of its official packages are fully ESM. If you want to use Payload within your own projects, make sure you are writing your scripts in ESM format or dynamically importing the Payload Config.
 </Banner>
 
-## Importing the Payload config outside of Next.js
+## Importing the Payload Config outside of Next.js
 
-Your Payload config likely has imports which need to be handled properly, such as CSS imports and similar. If you were to try and import your config without any Node support for SCSS / CSS files, you'll see errors that arise accordingly. 
+Your Payload Config likely has imports which need to be handled properly, such as CSS imports and similar. If you were to try and import your config without any Node support for SCSS / CSS files, you'll see errors that arise accordingly.
 
-This is especially relevant if you are importing your Payload config outside of a bundler context, such as in standalone Node scripts.
+This is especially relevant if you are importing your Payload Config outside of a bundler context, such as in standalone Node scripts.
 
-For these cases, you can use Payload's `importConfig` function to handle importing your config safely. It will handle everything you need to be able to load and use your Payload config, without any client-side files present.
+For these cases, you can use Payload's `importConfig` function to handle importing your config safely. It will handle everything you need to be able to load and use your Payload Config, without any client-side files present.
 
 Here's an example of a seed script that creates a few documents for local development / testing purposes, using Payload's `importConfig` function to safely import Payload, and the `getPayload` function to retrieve an initialized copy of Payload.
 
@@ -30,7 +30,7 @@ Here's an example of a seed script that creates a few documents for local develo
 // you should always use `import { getPayloadHMR } from '@payloadcms/next/utilities'` instead.
 import { getPayload } from 'payload'
 
-// This is a helper function that will make sure we can safely load the Payload config
+// This is a helper function that will make sure we can safely load the Payload Config
 // and all of its client-side files, such as CSS, SCSS, etc.
 import { importConfig } from 'payload/node'
 
@@ -43,7 +43,7 @@ import dotenv from 'dotenv'
 const filename = fileURLToPath(import.meta.url)
 const dirname = path.dirname(filename)
 
-// If you don't need to load your .env file, 
+// If you don't need to load your .env file,
 // then you can skip this part!
 dotenv.config({
   path: path.resolve(dirname, '../.env'),

docs/local-api/overview.mdx

@@ -55,9 +55,9 @@ import config from '@payload-config'
 const payload = await getPayloadHMR({ config })
 ```
 
-You should import Payload using the first option (`getPayloadHMR`) if you are using Payload inside of Next.js (like route handlers, server components, and similar.) 
+You should import Payload using the first option (`getPayloadHMR`) if you are using Payload inside of Next.js (like route handlers, server components, and similar.)
 
-This way, in Next.js development mode, Payload will work with Hot Module Replacement (HMR), and as you make changes to your Payload config, your usage of Payload will always be in sync with your changes. In production, `getPayloadHMR` simply disables all HMR functionality so you don't need to write your code any differently. We handle optimization for you in production mode.
+This way, in Next.js development mode, Payload will work with Hot Module Replacement (HMR), and as you make changes to your Payload Config, your usage of Payload will always be in sync with your changes. In production, `getPayloadHMR` simply disables all HMR functionality so you don't need to write your code any differently. We handle optimization for you in production mode.
 
 If you are accessing Payload via function arguments or `req.payload`, HMR is automatically supported if you are using it within Next.js.
 
@@ -73,7 +73,7 @@ const config = await importConfig('./payload.config.ts')
 const payload = await getPayload({ config })
 ```
 
-Both options function in exactly the same way outside of one having HMR support and the other not. However, when you import your Payload config, you need to make sure that you can import it safely. 
+Both options function in exactly the same way outside of one having HMR support and the other not. However, when you import your Payload Config, you need to make sure that you can import it safely.
 
 For more information about using Payload outside of Next.js, [click here](/docs/beta/local-api/outside-nextjs).