Update content/docs/internals/configuration.mdx

Co-authored-by: Kenneth Jenkins <[email protected]>

Author: gaurdro

content/docs/internals/configuration.mdx

@@ -57,7 +57,7 @@ For almost all use cases it's desirable to run in "all-in-one" mode. This reduce
 
 ### Discrete Services
 
-Split service mode is only advised for learning how the components interact, extremely security constrained environments or to workaround constraints in host environment.
+Split service mode is only advised for learning how the components interact, extremely security constrained environments or to work around constraints in host environment.
 
 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.