diff --git a/CONTRIBUTING.md b/CONTRIBUTING.md
index d20eab559c9..7afa8e0e7e2 100644
--- a/CONTRIBUTING.md
+++ b/CONTRIBUTING.md
@@ -136,7 +136,7 @@ All commit signatures must be verified to ensure that commits are coming from a
 
 ##### Setup pinentry-tty to handle headless environments
 
-When signing commits, gpg will need your passphrase to unlock the keyring. It usually uses a GUI pinentry program to do so. However on headless environments, this gets messy, so we highly recommend switching gpg to use a tty based pinentry to ease these problems.
+When signing commits, gpg will need your passphrase to unlock the keyring. It usually uses a GUI pinentry program to do so. However, on headless environments, this gets messy, so we highly recommend switching gpg to use a tty based pinentry to ease these problems.
 
 ```
 echo "pinentry-program $(which pinentry-tty)" >> ~/.gnupg/gpg-agent.conf
diff --git a/GOVERNANCE.md b/GOVERNANCE.md
index 11ae06cdbd1..2b1fa3235ad 100644
--- a/GOVERNANCE.md
+++ b/GOVERNANCE.md
@@ -44,7 +44,7 @@ We are currently looking to fill the position for two end-user community members
 
 In general, the Board makes decisions by lazy consensus with a minimum of participation based on the importance of the decisions to be made. Conversations happen on public GitHub for most cases, and through private e-mail for more sensitive issues.
 
-To make a decision the Board discusses the topic, a proposal is made, and a suitable wait time occurs for Board members to either agree or veto. By consensus we mean that any Board member can veto a decision with justification. By lazy we mean that not all Board members must participate, and that absence is interpreted as assent. By a minimum of participation we mean that we require the participation of a certain number of individuals based on the importance of the issue; for non-contentious issues a single Board member may move forward after a suitable time, while for contentious issues we will often require a few, often from different institutions.
+To make a decision the Board discusses the topic, a proposal is made, and a suitable wait time occurs for Board members to either agree or veto. By consensus, we mean that any Board member can veto a decision with justification. By lazy we mean that not all Board members must participate, and that absence is interpreted as assent. By a minimum of participation we mean that we require the participation of a certain number of individuals based on the importance of the issue; for non-contentious issues a single Board member may move forward after a suitable time, while for contentious issues we will often require a few, often from different institutions.
 
 ### Private communications of the Board
 
diff --git a/k8s/cloud/overlays/exposed_services_gclb/cloud_ingress.yaml b/k8s/cloud/overlays/exposed_services_gclb/cloud_ingress.yaml
index 866f60da6de..d4e1f6bf931 100644
--- a/k8s/cloud/overlays/exposed_services_gclb/cloud_ingress.yaml
+++ b/k8s/cloud/overlays/exposed_services_gclb/cloud_ingress.yaml
@@ -10,7 +10,7 @@ spec:
   rules:
   - http:
       paths:
-      # GCP does not support multiple wildcards so unfortunately we need this for each
+      # GCP does not support multiple wildcards, so unfortunately we need this for each
       # GRPC API service.
       - path: /pl.cloudapi.ArtifactTracker/
         pathType: Prefix