Apply suggestions from code review

Co-authored-by: Kobie Botha <[email protected]>

Author: rkistner

self-hosting/lifecycle-maintenance.mdx

@@ -66,7 +66,7 @@ The compact job uses up to 1GB memory for compacting, if available. Set the envi
 
 ### Load Balancer
 
-A load balancer is required in from of the API containers to provide TLS support and load balancing. Most cloud providers have built-in options for load balancing, such as ALB on AWS.
+A load balancer is required in front of the API containers to provide TLS support and load balancing. Most cloud providers have built-in options for load balancing, such as ALB on AWS.
 
 It is currently required to host the API container on a dedicated subdomain - we do not support running it on the same subdomain as another service.
 
@@ -86,7 +86,7 @@ server {
         proxy_set_header X-Real-IP $remote_addr;
         proxy_set_header X-Forwarded-For $proxy_add_x_forwarded_for;
 
-        # Disable proxy buffering - important for HTTP streaming connections
+        # Disable proxy buffering - important for HTTP streaming connections (configured in the PowerSync client SDK)
         proxy_buffering off;
     }
 }

self-hosting/lifecycle-maintenance/multiple-instances.mdx

@@ -26,6 +26,6 @@ Since each PowerSync instance maintains its own copy of the bucket data, the exa
 
 To ensure the same user always connects to the same endpoint, we recommend:
 1. Do an API lookup from the client application to get the PowerSync endpoint, don't hardcode it in the application.
-2. Either store the endpoint associated with each user, or compute it automatically using a hash function on the user id.
+2. Either store the endpoint associated with each user, or compute it automatically using a hash function on the user id e.g. `hash(user_id) % n` where `n` is your number of instances.