Apply suggestions from code review

Co-authored-by: Alex Krawiec <[email protected]>

Author: JoshuaMoelans

docs/platforms/native/advanced-usage/container-environments/index.mdx

@@ -4,14 +4,14 @@ description: "How to use the Sentry Native SDK in container environments."
 sidebar_order: 2000
 ---
 
-## Database-path on a mounted volume
+## Database Path on a Mounted Volume
 The Sentry Native SDK uses a [database path](https://docs.sentry.io/platforms/native/configuration/options/#database-path) to store events and crash reports. When you are using a containerized environment, you may want to mount a volume to persist the database across container restarts to avoid losing this data.
 
 ## Waiting for `Crashpad` to Finish
 Since SDK version [0.8.3](https://github.com/getsentry/sentry-native/releases/tag/0.8.3) the [option `crashpad_wait_for_upload`](https://docs.sentry.io/platforms/native/configuration/options/#crashpad-wait-for-upload) enables waiting for the `crashpad_handler` (on Linux) to finish its work before a shutdown-after-crash.
 
 
-In SDK versions before 0.8.3, one could use a script similar to the example below to tie container shutdown to the `crashpad_handler` process.
+In SDK versions older than 0.8.3, you could use a script similar to the example below to tie container shutdown to the `crashpad_handler` process:
 ```bash
 #!/bin/bash