Apply suggestions from code review

Co-authored-by: Burak Yigit Kaya <[email protected]>

Author: aldy505

develop-docs/self-hosted/reference-architecture/index.mdx

@@ -4,7 +4,7 @@ sidebar_title: Reference Architectures
 sidebar_order: 3
 ---
 
-This section contains reference architectures for self-hosted Sentry. These are not meant to be used as-is, but as a reference for how to deploy self-hosted Sentry around your existing infrastructure. This section can be used as a scaling strategy if you have higher traffic loads over time.
+This section contains reference architectures for self-hosted Sentry. These are not meant to be used as-is, but as a reference for how to deploy self-hosted Sentry around your existing infrastructure. This section can be used to create a scaling strategy if you have higher traffic loads over time.
 
-Please note that these reference architectures does not take into account external data storage dependencies such as Kafka, Postgres, Redis, S3 or other services. If you wish to do so, refer to the [Experimental Configurations](/self-hosted/experimental/) section
+Please note that these reference architectures do not take external data storage dependencies into account such as Kafka, Postgres, Redis, S3, etc. If you wish to do so, refer to the [Experimental Configurations](/self-hosted/experimental/) section
 <PageGrid />

develop-docs/self-hosted/reference-architecture/separate-ingest-box.mdx

@@ -81,5 +81,5 @@ sentry:
 While it's possible to run Relay on a different version than your self-hosted instance, we recommend keeping both Relay and Sentry on the same version. Remember to upgrade Relay whenever you upgrade your self-hosted Sentry installation.
 
 <Alert level="info" title="Fun Fact">
-  Sentry SaaS uses a similar setup for their ingestion servers, behind Google Anycast IP address.
+  Sentry SaaS uses a similar setup for its ingestion servers, behind Google Anycast IP addresses.
 </Alert>

develop-docs/self-hosted/reference-architecture/simple-single-node.mdx

@@ -6,9 +6,8 @@ sidebar_order: 1
 
 This is the simplest setup for self-hosted Sentry. It is recommended for small to medium-sized installations. This setup follows [the minimum requirements](/self-hosted/#required-minimum-system-resources) for running Sentry.
 
-It is highly recommended to put an external load balancer (or reverse proxy) in front of your self-hosted Sentry deployment. That way, you can tweak on rate limiting, TLS termination, and other features that does not change the built-in nginx configuration file. It is recommended to install the load balancer on your host machine instead of as a Docker container. Doing this way helps you in the event of Docker engine failure.
+It is highly recommended to put an external load balancer (or reverse proxy) in front of your self-hosted Sentry deployment. That way, you can tweak rate limiting, TLS termination, and other features and do not change the default `nginx` configuration file. It is recommended to install the load balancer directly on your host machine instead of running in a Docker container. This protects you against a Docker engine failure.
 
-If using external load balancer is not possible, you can put it as a Docker container, pointing to the `nginx` service at port `80`. Whatever value you put on your `SENTRY_BIND` environment variable won't matter.
 
 ```mermaid
 graph TB