nits

Author: brendan-kellam

docs/docs/connections/overview.mdx

@@ -43,12 +43,12 @@ A JSON configuration file is used to specify connections. For example:
 
 Configuration files must conform to the [JSON schema](#schema-reference).
 
-When running Sourcebot, this file must be mounted in a volume that is accessible to the container, with it's path specified in the `CONFIG_FILE` environment variable. For example:
+When running Sourcebot, this file must be mounted in a volume that is accessible to the container, with it's path specified in the `CONFIG_PATH` environment variable. For example:
 
 ```bash
 docker run \
     -v $(pwd)/config.json:/data/config.json \
-    -e CONFIG_FILE=/data/config.json \
+    -e CONFIG_PATH=/data/config.json \
     ... \ # other config
     ghcr.io/sourcebot-dev/sourcebot:latest
 ```

docs/docs/overview.mdx

@@ -72,7 +72,7 @@ Connect your code from multiple code-host platforms and search across all of the
 
 <Accordion title="Key benefits">
 - **Auto re-syncing:** Sourcebot will periodically sync with code hosts to pull the latest changes.
-- **Flexible configuration:** Sourcebot uses a expressive [JSON schema](/docs/connections/overview) config format to specify exaclty what repositories to index (and what not to index).
+- **Flexible configuration:** Sourcebot uses an expressive [JSON schema](/docs/connections/overview) config format to specify exactly what repositories to index (and what not to index).
 - **Parallel indexing:** Repositories are indexed in parallel.
 </Accordion>