Merge branch 'main' into ipip-car-order-signaling

Author: lidel

src/http-gateways/trustless-gateway.md

@@ -126,7 +126,7 @@ When the terminating entity at the end of the specified content path:
   specified byte range of that entity.
 
   - When dealing with a sharded UnixFS file (`dag-pb`, `0x70`) and a non-zero
-  `from` value, the UnixFS values `filesize` and `blocksizes` determine the
+  `from` value, the UnixFS data and `blocksizes`  determine the
   corresponding starting block for a given `from` offset.
 
 - cannot be interpreted as a continuous array of bytes (such as a DAG-CBOR/JSON

src/ipips/ipip-0402.md

@@ -1,7 +1,7 @@
 ---
 title: "IPIP-0402: Partial CAR Support on Trustless Gateways"
 date: 2023-04-17
-ipip: proposal
+ipip: ratified
 editors:
   - name: Hannah Howard
     github: hannahhoward
@@ -385,8 +385,8 @@ Use of the below fixture is highly recommended:
 - `QmYhmPjhFjYFyaoiuNzYv8WGavpSRDwdHWe5B4M5du5Rtk`
   from [`file-3k-and-3-blocks-missing-block.car`](https://github.com/ipfs/gateway-conformance/raw/v0.2.0/fixtures/trustless_gateway_car/file-3k-and-3-blocks-missing-block.car)
   for testing:
-  - `/ipfs/dag-pb-cid?format=car&dag-scope=entity&entity-bytes=0:1000` (only the blocks needed to fullfill the request, MUST succeed despite the fact that a block after the range is not retrievable)
-  - `/ipfs/dag-pb-cid?format=car&dag-scope=entity&entity-bytes=2200:*` (only the blocks needed to fullfill the request, MUST succeed despite the fact that a block before the range is not retrievable)
+  - `/ipfs/dag-pb-cid?format=car&dag-scope=entity&entity-bytes=0:1000` (only the blocks needed to fulfill the request, MUST succeed despite the fact that a block after the range is not retrievable)
+  - `/ipfs/dag-pb-cid?format=car&dag-scope=entity&entity-bytes=2200:*` (only the blocks needed to fulfill the request, MUST succeed despite the fact that a block before the range is not retrievable)
 
 :::
 

src/routing/http-routing-v1.md

@@ -205,9 +205,9 @@ This section contains a non-exhaustive list of known transfer protocols (by name
 
 ### Bitswap
 
-Multicodec name: `transport-bitswap`
-Schema: `bitswap`
-Specification: [ipfs/specs/BITSWAP.md](https://github.com/ipfs/specs/blob/main/BITSWAP.md)
+- Multicodec name: `transport-bitswap`
+- Schema: `bitswap`
+- Specification: [ipfs/specs/BITSWAP.md](https://github.com/ipfs/specs/blob/main/BITSWAP.md)
 
 #### Bitswap Read Provider Records
 
@@ -228,9 +228,9 @@ The server should respect a passed `transport` query parameter by filtering agai
 
 ### Filecoin Graphsync
 
-Multicodec name: `transport-graphsync-filecoinv1`
-Schema: `graphsync-filecoinv1`
-Specification: [ipfs/go-graphsync/blob/main/docs/architecture.md](https://github.com/ipfs/go-graphsync/blob/main/docs/architecture.md)
+- Multicodec name: `transport-graphsync-filecoinv1`
+- Schema: `graphsync-filecoinv1`
+- Specification: [ipfs/go-graphsync/blob/main/docs/architecture.md](https://github.com/ipfs/go-graphsync/blob/main/docs/architecture.md)
 
 #### Filecoin Graphsync Read Provider Records