editorial: clarify routing labels

Author: lidel

src/bitswap.md

@@ -28,7 +28,7 @@ editors:
     affiliation:
       name: Protocol Labs
       url: https://protocol.ai/
-tags: ['exchange']
+tags: ['exchange', 'routing']
 order: 1
 ---
 
@@ -40,6 +40,8 @@ Bitswap has two primary jobs:
 1. Attempt to acquire blocks from the network that have been requested by the client.
 2. Send blocks in its possession to other peers who want them.
 
+Secondary job (since [v1.2.0](#bitswap-1-2-0)) is to act as a basic content routing system for querying connected peers.
+
 ## Introduction
 
 Bitswap is a message-based protocol, as opposed to request-response. All messages
@@ -197,6 +199,13 @@ Given that a client *C* wants to fetch data from some server *S*:
   about that particular block. It SHOULD particularly send `Cancel` messages for
   `Block` requests (as opposed to `Have` requests) that have not yet been answered.
 
+:::note
+
+`Have`'s and `Have`/`DontHave` responses enable Bitswap to be used as
+bare-bones content routing system for connected peers.
+
+:::
+
 ### Bitswap 1.2.0: Wire Format
 
 ```protobuf

src/exchange/index.html

@@ -1,7 +1,7 @@
 ---
 title: Exchange
 description: |
-  Exchange is the way to for sending and receiving content addressed blocks of data.
+  Exchange is the way to for sending and receiving content-addressed blocks of data.
 ---
 
 {% include 'header.html' %}

src/index.html

@@ -82,15 +82,14 @@ <h3><a href="/meta/">Meta</a></h3>
       <section>
         <h3><a href="/routing/">Routing</a></h3>
         <p>
-          Routing is the way to determine where to find a given CID, Peer, or IPNS Record on the network;
-          specifically, which network peers provide specific CIDs.
+          Routing is the way to determine where to find a given content, peer, or IPNS record.
         </p>
         {% include 'list.html', posts: collections.routing %}
       </section>
       <section>
         <h3><a href="/exchange/">Exchange</a></h3>
         <p>
-          Exchange is the way to for sending and receiving content addressed blocks of data.
+          Exchange is the way to for sending and receiving content-addressed blocks of data.
         </p>
         {% include 'list.html', posts: collections.exchange %}
       </section>

src/routing/http-routing-v1.md

@@ -3,7 +3,7 @@ title: Delegated Routing V1 HTTP API
 description: >
   Delegated routing is a mechanism for IPFS implementations to use for offloading
   content routing and naming to another process/server. This specification describes
-  an HTTP API for delegated content routing.
+  an HTTP API for delegated routing of content, peers, and IPNS.
 date: 2023-08-31
 maturity: reliable
 editors:

src/routing/index.html

@@ -1,8 +1,7 @@
 ---
 title: Routing
 description: |
-  Routing is the way to determine where to find a given CID, Peer, or IPNS Record on the network;
-  specifically, which network peers provide specific CIDs.
+  Routing is the way to determine where to find a given content, peer, or IPNS record.
 ---
 
 {% include 'header.html' %}