capitalize Batch Worker

specification/docs/system-design.md

@@ -278,13 +278,13 @@ To achieve the Rollup requirements, the contract must do the following:
 
     1. This should be a payable method
 
-1. Implement a method for the current batch worker to initiate a Validation Pool targeting a Rollup Post that represents items from the batch queue.
+1. Implement a method for the current Batch Worker to initiate a Validation Pool targeting a Rollup Post that represents items from the batch queue.
 
     1. Items must be submitted in order without skipping any items
 
-1. Implement a method to select a new batch worker
+1. Implement a method to select a new Batch Worker
 
-    1. If this method is called to replace a batch worker who has failed to submit the next batch, a Validation Pool should be initiated and the batch worker's stakes submitted in favor of the VP. The DAO members may then stake against this VP, punishing the worker who failed to submit the batch.
+    1. If this method is called to replace a Batch Worker who has failed to submit the next batch, a Validation Pool should be initiated and the Batch Worker's stakes submitted in favor of the VP. The DAO members may then stake against this VP, punishing the worker who failed to submit the batch.
 
 **`AddItem`** Parameters
 
@@ -328,11 +328,11 @@ To achieve the Rollup requirements, the contract must do the following:
 
 1. For each included item, `stakeAmount` should be staked in favor of the VP on behalf of the Worker that submitted the item.
 
-1. The availability stake of the current batch worker should be staked in favor of the VP.
+1. The availability stake of the current Batch Worker should be staked in favor of the VP.
 
 1. The submitted items should be removed from the batch queue. 
 
-1. A new batch worker should be assigned.
+1. A new Batch Worker should be assigned.
 
 ## Automated Staking
 
@@ -397,7 +397,7 @@ In principle, we could define rules governing a Chat REP, that is distinct from
 
 Since Matrix Pools have no direct power over on-chain Reputation, Matrix Pools are always non-binding, meaning that Members who stake on the losing side of a Matrix Pool do not lose the staked REP. This is in contrast to on-chain Validation Pools, which may be anywhere from 0 to 100% binding.
 
-The main use case for Matrix Pools is in the context of the Rollup process. Rather than initiate an on-chain VP, a contract may add an item to the Rollup batch queue. The Rollup batch worker initiates a Matrix Pool for each of these items. Then, when the batch interval has elapsed, the Batch Worker submits a Batch Post whose authorship is determined by the outcomes of the corresponding Matrix Pools for the included batch items.
+The main use case for Matrix Pools is in the context of the Rollup process. Rather than initiate an on-chain VP, a contract may add an item to the Rollup batch queue. The Rollup Batch Worker initiates a Matrix Pool for each of these items. Then, when the batch interval has elapsed, the Batch Worker submits a Batch Post whose authorship is determined by the outcomes of the corresponding Matrix Pools for the included batch items.
 
 Like on-chain VPs, Matrix Pools have three operations: Initiate Pool, Stake, and Evaluate Outcome. All Worker clients which intend to participate in the on-chain VP targeting the next Batch Post should listen for and handle these messages.