diff --git a/src/ipips/ipip-0402.md b/src/ipips/ipip-0402.md
index 9176ae8a9..7de1f054b 100644
--- a/src/ipips/ipip-0402.md
+++ b/src/ipips/ipip-0402.md
@@ -88,7 +88,7 @@ Terse rationale for each feature:
 
 - Trustless HTTP Clients will be able to fetch a CAR with a file, byte range,
   or a directory enumeration using a way lower number of HTTP requests, which
-  will translate to improved resouce utilization, longer battery time on
+  will translate to improved resource utilization, longer battery time on
   mobile, and lower latency due to lower number of round trips.
 
 - CAR files downloaded from HTTP Gateways will always be end-to-end verifiable.
@@ -104,7 +104,7 @@ Terse rationale for each feature:
     - [HTTP retrieval in Boost](https://boost.filecoin.io/http-retrieval)
     - [bifrost-gateway](https://github.com/ipfs/bifrost-gateway)
 
-- Trustless Gateway is solidifed as the ecosystem wide standard.
+- Trustless Gateway is solidified as the ecosystem wide standard.
 
   - IPIP tests added to
     [gateway-conformance](https://github.com/ipfs/gateway-conformance) test
@@ -113,7 +113,7 @@ Terse rationale for each feature:
 
   - End users are empowered with primitives and tools that reduce retrieval
     cost, encourage self-hosting, or make validation of conformance claims of
-    free or comercial gateways possible.
+    free or commercial gateways possible.
 
 ### Compatibility
 
@@ -174,7 +174,7 @@ Due to this, gateway specification changes introduced in this IPIP clarify that:
 - The CAR `roots` behavior is out of scope and flags that clients MAY ignore it.
 - CAR determinism is not present by default, responses may differ across
   requests and gateways.
-- Opt-in determinism is possible, but standarized signaling mechanism does not
+- Opt-in determinism is possible, but standardized signaling mechanism does not
   exist until we have IPIP-412 or similar.
 
 ### Security
@@ -213,7 +213,7 @@ knows it has child entity named `index.html`, and everyone would pay a lower cos
 to lower number of blocks being returned in a single round-trip, instead of two.
 
 Rhea/Saturn projects requested this to be out of scope for now, but this "web"
-entity scope could be added in the future, as a follow-up optimiziation IPIP.
+entity scope could be added in the future, as a follow-up optimization IPIP.
 
 #### Requesting specific DAG depth
 
@@ -234,7 +234,7 @@ Relevant tests were added to
 [gateway-conformance](https://github.com/ipfs/gateway-conformance) test suite
 in [#56](https://github.com/ipfs/gateway-conformance/pull/56) and
 [#85](https://github.com/ipfs/gateway-conformance/issues/85).
-Detailed list of compliance checks for `dag-scope` and `entity-bytes` can be found in
+A detailed list of compliance checks for `dag-scope` and `entity-bytes` can be found in
 [`v0.2.0/trustless_gateway_car_test.go`](https://github.com/ipfs/gateway-conformance/blob/v0.2.0/tests/trustless_gateway_car_test.go) or later.
 
 Below are CIDs, CARs, and short summary of each fixture.