Docs improvements

README.md

@@ -16,7 +16,7 @@ An overview of the different projects, in order of relevance and interest:
 
 ## Participating
 
-Brief technical overview of participating in the MPC. Further information available [here](https://app.gitbook.com/@aztec-protocol/s/mpc).
+Brief technical overview of participating in the MPC. Further information is available [here](https://app.gitbook.com/@aztec-protocol/s/mpc).
 
 #### The Easy Way
 

ci-scripts/build.sh

@@ -3,7 +3,7 @@ set -e
 
 IMAGE_NAME=$1
 
-# Docker layer caching can have old layers. Pull given images from remote if we haven't rebuilt this run.
+# Docker layer caching can have old layers. Pull the given images from the remote if we haven't rebuilt this run.
 for DEP in $2; do
   if [ ! -f /tmp/${DEP#*/}.rebuilt ]; then
     docker pull $DEP:latest
@@ -15,4 +15,4 @@ if [ -n "$CIRCLE_SHA1" ]; then
   docker tag $IMAGE_NAME:latest $IMAGE_NAME:$CIRCLE_SHA1
 fi
 
-touch /tmp/${IMAGE_NAME#*/}.rebuilt
+touch /tmp/${IMAGE_NAME#*/}.rebuilt

setup-iac/main.tf

@@ -28,7 +28,7 @@ resource "aws_vpc" "setup" {
   }
 }
 
-# We create an addional CIDR block to expand beyond initial /16 limits.
+# We create an additional CIDR block to expand beyond initial /16 limits.
 resource "aws_vpc_ipv4_cidr_block_association" "cidr1" {
   vpc_id     = aws_vpc.setup.id
   cidr_block = "10.1.0.0/16"

setup-iac/us-east-2/main.tf

@@ -31,7 +31,7 @@ resource "aws_vpc" "setup" {
   }
 }
 
-# We create an addional CIDR block to expand beyond initial /16 limits.
+# We create an additional CIDR block to expand beyond initial /16 limits.
 resource "aws_vpc_ipv4_cidr_block_association" "cidr1" {
   vpc_id     = aws_vpc.setup.id
   cidr_block = "10.3.0.0/16"

setup-mpc-client-bash/README.md

@@ -5,7 +5,7 @@ This project contains a few bash scripts which can be used as a reference as to
 ## Requirements
 
 - You need to be running [setup-mpc-client](../setup-mpc-client) with the environment variable `COMPUTE_OFFLINE=1`.
-- You need to be running an ETH node such as ganache configured with the account that you will use to verify with the server.
+- You need to be running an ETH node such as a ganache configured with the account that you will use to verify with the server.
 
 ## Usage
 

setup-mpc-client/README.md

@@ -11,7 +11,7 @@ Participants in the AZTEC trusted setup multi party computation fall into three
 2. **Early bird individuals** - Participants that have signed up for the ceremony prior to the _selection date_. They have secondary priority during the ceremony.
 3. **Individuals** - Participants that have signed up for the ceremony after the _selection date_, or who were not choosen during selection. They have tertiary priority during the ceremony.
 
-The _selection date_ is goverened by a predetermined Ethereum block height. The block hash of the block is used as a seed to a pseudo random number generator which first selects a number of participants from tier 2, and is then used to randomise the priority order of participants in both tier 1 and tier 2. Unselected participants and participants in tier 3 are ordered on a first come first served basis.
+The _selection date_ is goverened by a predetermined Ethereum block height. The block hash of the block is used as a seed to a pseudo random number generator which first selects a number of participants from tier 2, and is then used to randomize the priority order of participants in both tier 1 and tier 2. Unselected participants and participants in tier 3 are ordered on a first come first served basis.
 
 To sign up for participation, a user must send 1 wei to the AZTEC controlled address `0x000000000xxxxxxx0000000`. The private key of the sending address must be provided to the client application for authentication.
 

setup-mpc-map/src/shooting-stars.ts

@@ -7,7 +7,7 @@ export class ShootingStars {
   constructor(locations: LatLon[], viewer: Cesium.Viewer) {
     const baseTime = viewer.clock.startTime;
 
-    // Stick first location on the end, so we get a loop. Remove duplicate contiguous locations.
+    // Stick the first location on the end, so we get a loop. Remove duplicate contiguous locations.
     locations = [...locations, locations[0]].filter(
       (el, i, a) => i === 0 || (el.lat !== a[i - 1].lat || el.lon !== a[i - 1].lon)
     );

setup-mpc-server/README.md

@@ -84,7 +84,7 @@ The text `SignMeWithYourPrivateKey`, signed by the admin address.
 
 `PATCH /api/participant/<address>`
 
-Updates telemetry around a participants progress.
+Updates telemetry around a participant's progress.
 
 `Body`