Updated Production Setup (markdown)

Production-Setup.md

@@ -2,16 +2,16 @@ A robust production setup requires more configuration -- and care -- than the
 [[Getting Started]] guide. There are multiple layers of components. Please follow
 the steps to set them up from bottom up, one by one.
 
-* Setup object storage
-  * Setup Masters
+* Set up object storage
+  * Set up Masters
   * Add volume servers
-* Setup file storage
+* Set up file storage
   * Choose filer store
   * Setup Filer
 
-And then, choose the component you want to setup
-* Setup S3
-* Setup FUSE mount
+And then, choose the component you want to set up
+* Set up S3
+* Set up FUSE mount
 * Cluster Maintenance
 
 ## Prerequisites
@@ -25,8 +25,8 @@ Make sure the ports are open. By default
 | Filer | 8888 | 18888 |
 | S3 | 8333 | |
 
-If you have multi-homed servers (many IP addresses and interfaces), you need
-to ensure SeaweedFS uses the correct IP, for cluster communication. Append
+If you have multi-homed servers (many IP addresses and interfaces),
+ensure SeaweedFS uses the correct IP for cluster communication. Append
 `-ip=xx.xx.xx.xx` to specify the appropriate address. 
 
 If you wish to use a different IP address for user-facing services, then 
@@ -46,17 +46,17 @@ empty spaces, you need to reduce the volume size.
 weed server -filer -s3 -ip=xx.xx.xx.xx -volume.max=0 -master.volumeSizeLimitMB=1024
 ```
 
-# Setup object storage
+# Set up object storage
 
-## Setup Masters
+## Set up Masters
 
 ### One master is fine
 
-If there are 2 machines, it is not possible to achieve consensus. Just do not bother to setup multiple masters. 
+If there are 2 machines, it is not possible to achieve consensus. Just do not bother to set up multiple masters. 
 
 Even for large clusters, it is totally fine to have one single master. The load on master is very light. It is unlikely to go down. You can always just restart it since it only has soft states collected from volume servers.
 
-### Setup masters
+### Set up masters
 
 OK. Your CTO just wants multiple masters. To do so, see [[Failover Master Server]] for details.
 
@@ -115,12 +115,12 @@ Additional notes:
 
 Now the object store setup is completed. You can visit `http://<master>:9333/` to check it around.
 
-* Make sure the Free volume count is not zero.
-* Try to assign some file ids to trigger a volume allocation. 
+* Ensure the Free volume count is not zero.
+* Try to assign some file IDs to trigger a volume allocation. 
 
 If you only use SeaweedFS object store, that is all.
 
-# Setup file storage
+# Set up file storage
 
 ## Choose filer store
 
@@ -161,7 +161,7 @@ weed filer -s3 -s3.config=<config.json> -port=8333
 
 The endpoint is `http://<s3_server_host>:8333`.
 
-## Setup FUSE mount
+## Set up FUSE mount
 
 Run
 
@@ -174,7 +174,7 @@ Run
 
 ## Cluster Maintenance
 
-In a cluster, volume servers can go down. But automatic rebalancing will be problematic. It can cause unexpected busy network activities. For example, the heartbeat of a volume server may come and go, causing unnecessary busy system. Current recommended strategy is to keep existing data readonly, and automatically add new writable volumes.
+In a cluster, volume servers can go down. But automatic rebalancing will be problematic. It can cause unexpected busy network activities. For example, the heartbeat of a volume server may come and go, causing an unnecessarily busy system. Currently recommended strategy is to keep the existing data readonly, and automatically add new writable volumes.
 
 There are `volume.balance` and `volume.fix.replication` commands in `weed shell`. You can configure them to run during off hours.