update

Author: okdistribute

concepts/endpoints.mdx

@@ -4,24 +4,35 @@ title: "Endpoints"
 
 An _endpoint_ is the main API interface to create connections to, and accept
 connections from other iroh endpoints. The connections are peer-to-peer and
-encrypted, a [Relay](/concepts/relays) server is used to make the
-connections reliable. Endpoints have a `EndpointID` (the public half of an
+end-to-end encrypted. Endpoints have a `EndpointID` (the public half of an
 Ed25519 keypair) and the private key used to sign and decrypt messages.
 
-Generally, an application will have a single endpoint instance. This ensures all the connections made share the same peer-to-peer connections to other iroh endpoints, while still remaining independent connections. This will result in more optimal network behaviour.
+Generally, an application will have a single endpoint instance. This ensures all
+the connections made share the same peer-to-peer connections to other iroh
+endpoints, while still remaining independent connections. This will result in
+more optimal network behaviour.
 
 
 ## Endpoint Identifiers
 
-Each endpoint in iroh has a unique identifier (`EndpointID`) created as a cryptographic key. This can be used to globally identify an endpoint. Because `EndpointIDs` are cryptographic keys, they are also the mechanism by which all traffic is always encrypted for a specific endpoint only.
+Each endpoint in iroh has a unique identifier (`EndpointID`) created as a
+cryptographic key. This can be used to globally identify an endpoint. Because
+`EndpointIDs` are cryptographic keys, they are also the mechanism by which all
+traffic is always encrypted for a specific endpoint only.
 
-See the [EndpointID](https://docs.rs/iroh/latest/iroh/type.EndpointId.html) documentation for more info.
+See the [EndpointID](https://docs.rs/iroh/latest/iroh/type.EndpointId.html) documentation for more information.
 
 ## Connections
 
-Because we're in a peer-2-peer context, either endpoint might be operating as the "server", so we use `connect` and `accept` to distinguish between the two. The `connect` method is used to create a new connection to a remote endpoint, while `accept` is used to accept incoming connections from a remote endpoint.
+Because we're in a peer-2-peer context, either endpoint might be operating as
+the "server", so we use `connect` and `accept` to distinguish between the two.
+The `connect` method is used to create a new connection to a remote endpoint,
+while `accept` is used to accept incoming connections from a remote endpoint.
 
-Connections are full-fledged QUIC connections, giving you access to most features of QUIC / HTTP3, including bidirectional and unidirectional streams.
+Connections are full-fledged QUIC connections, giving you access to most
+features of QUIC / HTTP3, including bidirectional and unidirectional streams.
+
+A [Relay](/concepts/relays) server can be used to make the connections reliable.
 
 <Note>
 Due to the light-weight properties of QUIC streams a stream can only be accepted once the initiating peer has sent some data on it.
@@ -32,6 +43,6 @@ Due to the light-weight properties of QUIC streams a stream can only be accepted
 Endpoints are a low-level primitive that iroh exposes on purpose. For some
 projects like [dumbpipe](https://dumbpipe.dev), endpoints are 95% of what you
 need to connect any two devices on the planet. For others, like
-[iroh-blobs](/proto/iroh-blobs), endpoints are the foundation that higher-level
+[Blobs](/protocols/blobs), endpoints are the foundation that higher-level
 protocols are built on. Most projects will not work with endpoints beyond
 constructing one and feeding it to one or more [protocols](/concepts/protocols).

concepts/protocols.mdx

@@ -69,7 +69,7 @@ to quickly add functionality, work directly with QUIC streams & build a fully
 custom protocol that does exactly what you want, or fork an existing protocol to
 get what you need.
 
-- [iroh-gossip](/connecting/gossip): creating swarms of peers for broadcasting messages on topics.
-- [iroh-blobs](/protocols/blobs): storing and transferring large binary blobs of data.
-- [iroh-docs](/protocols/docs): collaborative key-value store. 
+- [Gossip Broadcast](/connecting/gossip): creating swarms of peers for broadcasting messages on topics.
+- [Blobs](/protocols/blobs): storing and transferring large binary blobs of data.
+- [Key-value CRDTs](/protocols/kv-crdts): collaborative key-value store. 
 - [Writing Custom Protocols](/protocols/writing-a-protocol): guide on building your own protocols on top of iroh.

connecting/creating-endpoint.mdx

@@ -6,16 +6,26 @@ An endpoint is the core building block of an iroh node. It manages network
 connections, handles incoming and outgoing traffic, and provides the necessary
 infrastructure for implementing protocols.
 
-To create an endpoint in Iroh, you can use the `Endpoint::bind` method. This
-method initializes a new endpoint and binds it to a local address, allowing it
+Once you have an Endpoint, you can use it to create connections or accept incoming connections from other endpoints.
+
+Unlike HTTP servers, which listen on specific ports, iroh Endpoints use a peer-to-peer
+model to establish connections. This means that endpoints can connect directly
+to each other without relying on a central server.
+
+This means that endpoints can be more resilient to network issues and can operate in
+a wider range of network environments.
+
+## Creating an Endpoint
+
+This method initializes a new endpoint and binds it to a local address, allowing it
 to listen for incoming connections.
 
 ```rust
 use iroh::Endpoint;
 
 #[tokio::main]
 async fn main() {
-    let endpoint = Endpoint::bind().await.unwrap();
+    let endpoint = Endpoint::builder().bind().await?;
     // ...
 }
 ```
@@ -25,5 +35,3 @@ async fn main() {
 incoming connections
 2. `await` keyword is used to wait for the endpoint
 to be created in an asynchronous context.
-3. Once you have an endpoint, you can use it to create connections to other
-endpoints, or accept incoming connections from other endpoints.

deployment/security-privacy.mdx

@@ -38,5 +38,5 @@ abuse, we reserve the right to block offending IP addresses or users from
 accessing the public relays.
 
 To learn more about deploying and managing your own relays, see the
-[n0des](//managing-relays) documentation.
+[n0des documentation](/managing-relays).
 

docs.json

@@ -20,8 +20,7 @@
               "quickstart",
               "examples",
             {
-              "group": "Concepts",
-              "expanded": true,
+              "group": "How it works",
               "pages": [
                 "concepts/endpoints",
                 "concepts/discovery",