From ee9b62ee24ca12f7797535d3f9bc71e5eb542ceb Mon Sep 17 00:00:00 2001
From: Daniel N <2color@users.noreply.github.com>
Date: Fri, 27 Sep 2024 11:28:44 +0200
Subject: [PATCH] fix: linting

---
 src/ipips/ipip-0484.md | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)

diff --git a/src/ipips/ipip-0484.md b/src/ipips/ipip-0484.md
index 1f326db5..eb9a7086 100644
--- a/src/ipips/ipip-0484.md
+++ b/src/ipips/ipip-0484.md
@@ -64,7 +64,7 @@ The proposed change is to add a `?filter-protocols` parameter to the `GET /routi
 
 - Add a `?filter-protocols=<comma-separated-list>` optional parameter to `GET /routing/v1/providers/{CID}` to filter providers based on the `Protocol` field of the [Peer schema].
 - The `filter-protocols` parameter is a comma-separated list of transfer protocol names, e.g. `?filter-protocols=transport-bitswap`.
-- Transfer protocols names should be treated as opaque strings and have a max length of 63 characters. A non-exhaustive list of transfer protocols are defined per convention in the [multicodec registry](https://github.com/multiformats/multicodec/blob/3b7b52deb31481790bc4bae984d8675bda4e0c82/table.csv#L149-L151). 
+- Transfer protocols names should be treated as opaque strings and have a max length of 63 characters. A non-exhaustive list of transfer protocols are defined per convention in the [multicodec registry](https://github.com/multiformats/multicodec/blob/3b7b52deb31481790bc4bae984d8675bda4e0c82/table.csv#L149-L151).
 - Implementations MUST ignore unknown transfer protocol names.
 - `unknown` can be be passed to include providers whose transfer protocol is unknown, e.g. `?filter-protocols=unknown`. This allows filtering providers returned from the DHT that do not contain explicit transfer protocol information.
 - Providers are filtered by checking if the transfer protocol name appears in the `Protocols` array (logical OR).