title casing

docs/content/1.getting-started/3.configuration.md

@@ -2,7 +2,7 @@
 
 By default, Nuxt is configured to cover most use cases. The [`nuxt.config.ts`](/guide/directory-structure/nuxt.config) file can override or extend this default configuration.
 
-## Nuxt configuration
+## Nuxt Configuration
 
 The `nuxt.config.ts` file is located at the root of a Nuxt project and can override or extend the application's behavior.
 
@@ -24,7 +24,7 @@ Every configuration option is described in the [Configuration Reference](/api/co
 You don't have to use TypeScript to build an application with Nuxt. However, it is strongly recommended to use the `.ts` extension for the `nuxt.config` file. This way you can benefit from hints in your IDE to avoid typos and mistakes while editing your configuration.
 ::
 
-### Environment variables and private tokens
+### Environment Variables and Private Tokens
 
 The `runtimeConfig` API exposes values like environment variables to the rest of your application. By default, these keys are only available server-side. The keys within `runtimeConfig.public` are also available client-side.
 
@@ -62,7 +62,7 @@ const runtimeConfig = useRuntimeConfig()
 
 :ReadMore{link="/guide/going-further/runtime-config"}
 
-## App configuration
+## App Configuration
 
 The `app.config.ts` file, also located at the root of a Nuxt project, is used to expose public variables that can be determined at build time. Contrary to the `runtimeConfig` option, these can not be overriden using environment variables.
 
@@ -90,7 +90,7 @@ const appConfig = useAppConfig()
 
 :ReadMore{link="/guide/directory-structure/app.config"}
 
-## `runtimeConfig` or `app.config`
+## `runtimeConfig` vs `app.config`
 
 As stated above, `runtimeConfig` and `app.config` are both used to expose variables to the rest of your application. To determine whether you should use one or the other, here are some guidelines: