pre-commit changes

Author: gaurdro

content/docs/internals/configuration.mdx

@@ -33,13 +33,11 @@ See the [reference](/docs/reference) page for a complete list of available optio
 
 ## All-In-One vs Split Service mode
 
-Pomerium's default mode is all-in-one mode. It run all the indivudual [components](/docs/internals/architecture#component-level) in a single container or under a single system service. This is our suggested way to run Pomerium.  Alternatively, each of those component services can be configured and run separately in split mode.
+Pomerium's default mode is all-in-one mode. It run all the individual [components](/docs/internals/architecture#component-level) in a single container or under a single system service. This is our suggested way to run Pomerium. Alternatively, each of those component services can be configured and run separately in split mode.
 
-All-in-one mode has the easiest configuration and successfully used in large production environments.  All the configuration goes in a single `config.yaml` file or single set of environment variables.
-When running Pomerium as a single system service or container, all the options on this page can be set in a single `config.yaml` file, or passed to the single instance as environment variables. Internal communication is configured automatically requiring no addtional setup. 
-
-Alternatively, each component can be run separately in split-mode using the [service mode](/docs/reference/service-mode) key to specify which component to run.  Each of these needs to be configured separately, and communication between components must be explicitly configured including managing tls certificates.
+All-in-one mode has the easiest configuration and successfully used in large production environments. All the configuration goes in a single `config.yaml` file or single set of environment variables. When running Pomerium as a single system service or container, all the options on this page can be set in a single `config.yaml` file, or passed to the single instance as environment variables. Internal communication is configured automatically requiring no additional setup.
 
+Alternatively, each component can be run separately in split-mode using the [service mode](/docs/reference/service-mode) key to specify which component to run. Each of these needs to be configured separately, and communication between components must be explicitly configured including managing tls certificates.
 
 ## Service Mode
 
@@ -61,8 +59,7 @@ For almost all use cases it's desirable to run in "all-in-one" mode. This reduce
 
 Split service mode is only advised for learning how the components interact, extremely security constrained environments or to workaround constraints in host environment.
 
-The split service mode can limit the blast radius in the event of a compromised container and can enable independet scaling of components.  These features come with some downsides. There will be increased latency to the authorize service, which is consulted on every request. In addition to complicating upgrades, the additional configuration makes debugging configuration errors more difficult.
-In larger footprints, it is recommended to run Pomerium as a collection of discrete service clusters. This limits blast radius in the event of vulnerabilities and allows for per-service [scaling](#scaling) and monitoring.
+The split service mode can limit the blast radius in the event of a compromised container and can enable independent scaling of components. These features come with some downsides. There will be increased latency to the authorize service, which is consulted on every request. In addition to complicating upgrades, the additional configuration makes debugging configuration errors more difficult. In larger footprints, it is recommended to run Pomerium as a collection of discrete service clusters. This limits blast radius in the event of vulnerabilities and allows for per-service [scaling](#scaling) and monitoring.
 
 Please also see [Architecture](/docs/internals/architecture) for information on component interactions.