chore: fix some comments

website/docs/contribute/bugreports.md

@@ -12,7 +12,7 @@ Bug reports are critical to the rapid development of the Prysm client. In order
 
 ## Checking if your issue exists
 
-Duplicate tickets are a hinderance to the development process and, as such, it is crucial to first check through Prysm's existing issues to see if what you are experiencing has already been indexed.
+Duplicate tickets are a hindrance to the development process and, as such, it is crucial to first check through Prysm's existing issues to see if what you are experiencing has already been indexed.
 
 To do so, head over to the [issue page](https://github.com/prysmaticlabs/prysm/issues) and enter some related keywords into the search bar. This may include a sample from the output or specific components it affects. If this is unsuccessful, check the [issue labels index](https://github.com/prysmaticlabs/prysm/labels) for related categories and review the tickets within.
 

website/docs/contribute/contribution-guidelines.md

@@ -63,7 +63,7 @@ Please define the following environment variable when running tests:
 
     CGO_CFLAGS="-O2 -D__BLST_PORTABLE__"
 
-It is particulary useful when running tests / debug in your IDE without using bazel.
+It is particularly useful when running tests / debug in your IDE without using bazel.
 
 See the [next section](#building-and-testing-prysm-with-bazel) for instructions on testing with prysm.
 

website/docs/devtools/net-design.md

@@ -33,7 +33,7 @@ A high level overview of the proposed design. This states the components of the
 
 **Transport**
 
-For network transport we must be able to support TCP connections (UDP not a requirement). We have to be able to manage inbound and outbound tcp connections. Although not a requirement for mainnet, for interoperability all clients will have to be able to support an IPv4 endpoint. Any listening endpoints must be publically communicable, so Circuit Relays, AutoNat, etc are not applicable. 
+For network transport we must be able to support TCP connections (UDP not a requirement). We have to be able to manage inbound and outbound tcp connections. Although not a requirement for mainnet, for interoperability all clients will have to be able to support an IPv4 endpoint. Any listening endpoints must be publicly communicable, so Circuit Relays, AutoNat, etc are not applicable. 
 
 **Current Status in Prysm**
 

website/docs/how-prysm-works/database-backend-boltdb.md

@@ -20,7 +20,7 @@ After testing and benchmarking all three options, Bolt was decided upon as the b
 
 ## BoltDB functionality
 
-All database related logic is contained in the `db/` directory of the Prysm repository. Given that BoltDB is a [key-value store](/docs/terminology#key-value-store) backend, 'buckets' \(akin to tables in relational databases\) are required for data storage. Blocks, transactions, state, proposals and attestations are are all defined in these buckets, in what is known as 'bucket data'.
+All database related logic is contained in the `db/` directory of the Prysm repository. Given that BoltDB is a [key-value store](/docs/terminology#key-value-store) backend, 'buckets' \(akin to tables in relational databases\) are required for data storage. Blocks, transactions, state, proposals and attestations are all defined in these buckets, in what is known as 'bucket data'.
 
 ### Example: bucket creation
 

website/docs/install/install-with-docker.md

@@ -391,7 +391,7 @@ docker run -it -v %LOCALAPPDATA%\Eth2:/data -p 4000:4000 -p 13000:13000 -p 12000
 :::info
 `http-host` and `http-port` have replaced `--grpc-gateway-host` and `--grpc-gateway-port` respectively.
 :::
-This tells your Docker container to to "listen" for connections from outside of your container, allowing you (and other services) to reach your RPC endpoint(s). See [Configure ports and firewalls](../prysm-usage/p2p-host-ip.md) for more information.
+This tells your Docker container to "listen" for connections from outside of your container, allowing you (and other services) to reach your RPC endpoint(s). See [Configure ports and firewalls](../prysm-usage/p2p-host-ip.md) for more information.