Libp2p curriculum reordering

Author: walker

content/en/curriculum/libp2p/connections/index.md

@@ -5,7 +5,7 @@ draft: false
 menu:
     curriculum:
         parent: "curriculum-libp2p"
-weight: 310
+weight: 40
 category: lecture
 level:
 - shallow
@@ -186,7 +186,7 @@ Because the data will be sent over the same connection, we need an abstraction c
 
 ### Negotiating protocols
 
-After the connection is established (i.e. handshake, security, and multiplexing), peers exchange what application protocols they support. Because `multistream-select` is used, the procedure to agree on an application protocol is the same as for the security and mutiplexing negotiations: the protocol identifier is sent to the peer and `na` is answered if the protocol is not supported.
+After the connection is established (i.e. handshake, security, and multiplexing), peers exchange what application protocols they support. Because `multistream-select` is used, the procedure to agree on an application protocol is the same as for the security and multiplexing negotiations: the protocol identifier is sent to the peer and `na` is answered if the protocol is not supported.
 
 Every supported protocol is assigned a handler, which manages the data for that protocol.
 

content/en/curriculum/libp2p/core-concepts/index.md

@@ -5,7 +5,7 @@ draft: false
 menu:
     curriculum:
         parent: "curriculum-libp2p"
-weight: 300
+weight: 30
 category: lecture
 goal: 1.2
 subgoals:

content/en/curriculum/libp2p/dht/index.md

@@ -5,7 +5,7 @@ draft: false
 menu:
     curriculum:
         parent: "curriculum-libp2p"
-weight: 315
+weight: 50
 category: lecture
 level:
 - deep

content/en/curriculum/libp2p/introduction.md

@@ -5,7 +5,7 @@ draft: false
 menu:
     curriculum:
         parent: "curriculum-libp2p"
-weight: 290
+weight: 20
 category: lecture
 level:
 - shallow
@@ -30,6 +30,15 @@ This is the stuff that moves libp2p from "a networking toolbox to build P2P appl
 
 [Node data dashboard](https://kademlia-exporter.max-inden.de/d/-avwMhsik/kademlia-exporter?orgId=1)
 
+## libp2p Introduction
+
+This recording and deck is intended to provide a high-level overview of the fundamental concepts of libp2p.
+
+{{< youtube Xw-5cRSs85M>}}
+
+{{< embed src="https://docs.google.com/presentation/d/e/2PACX-1vSBFLQibkm_YWUi0sIaY7CLLd4PMpPk0kjgE1nt5XPBuHwhTU0owdCP44nv5OzBmoDAOIwcy4Ngx0AV/embed?start=false&loop=false&delayms=3000" frameborder="0" width="100%" height="500" allowfullscreen="true" mozallowfullscreen="true" webkitallowfullscreen="true" >}}
+Introduction to libp2p (3/9/23)
+
 ### Introduction to libp2p | David Dias
 
 {{< youtube CRe_oDtfRLw >}}
@@ -78,7 +87,7 @@ The users of the libp2p protocol suite include, and is a list that is always bei
 **Resources:**
 * [Blog with Pubsub instructions](https://bitly.protocol.ai/pubsub-blog)
 * [Other Pubsub Options](https://bitly.protocol.ai/pusub-flags)
-* [lipbp2p Docs – Publish/Subscribe](https://docs.libp2p.io/concepts/publish-subscribe/)
+* [libp2p Docs – Publish/Subscribe](https://docs.libp2p.io/concepts/publish-subscribe/)
 
 ### Links
 

content/en/curriculum/libp2p/nat-traversal/index.md

@@ -5,7 +5,7 @@ draft: false
 menu:
     curriculum:
         parent: "curriculum-libp2p"
-weight: 350
+weight: 70
 category: lecture
 level:
 - deep
@@ -76,9 +76,9 @@ This includes two types of hosts: publicly reachable and non-publicly reachable
 
 _See_ [_the full proposal here_](https://github.com/protocol/web3-dev-team/pull/21/files#diff-b137dc3a933796d3ce264eeb6a31386d72a7a1c925c01e62c3ab026f46c417c2)
 
-Given the pervasiveness of IPv4 peers that are behind NATs on the internet, NAT traversal is an essential requirement for a peer to peer application. The inability to traverse NATs means that such NATT’d peers are NOT reachable on the network and are thus unable to provide any meaningful service to the network. Nor can they interact with network participants under protocol patterns that require inbound connections (e.g. dialbacks).
+Given the pervasiveness of IPv4 peers that are behind NATs on the internet, NAT traversal is an essential requirement for a peer to peer application. The inability to traverse NATs means that such NAT’d peers are NOT reachable on the network and are thus unable to provide any meaningful service to the network. Nor can they interact with network participants under protocol patterns that require inbound connections (e.g. dialbacks).
 
-libp2p currently executes NAT traversal using[ Circuit Relays](https://docs.libp2p.io/concepts/circuit-relay/) wherein publicly dialable Relay servers relay the entirety of user traffic to peers that are NATT’d. This approach does NOT scale because:
+libp2p currently executes NAT traversal using[ Circuit Relays](https://docs.libp2p.io/concepts/circuit-relay/) wherein publicly dialable Relay servers relay the entirety of user traffic to peers that are NAT’d. This approach does NOT scale because:
 
 1. It costs bandwidth on the Relay server.
 2. There is NO real incentive to be a Relay server.

content/en/curriculum/libp2p/objectives/index.md

@@ -6,7 +6,7 @@ menu:
     curriculum:
         parent: "curriculum-libp2p"
         identifier: "libp2p-objectives"
-weight: 289
+weight: 10
 category: lecture
 level:
 - shallow

content/en/curriculum/libp2p/past-recorded-sessions.md

@@ -1,5 +1,5 @@
 ---
-title: "Past Recorded Sessions For Libp2p"
+title: "Libp2p Shallow and Deep Dive Sessions"
 description: "Introductory, Shallow & Deep Dives into libp2p"
 draft: false
 menu:
@@ -9,15 +9,6 @@ weight: 170
 category: lecture
 ---
 
-## libp2p Introduction
-
-This recording and deck is intended to provide a high-level overview of the fundamental concepts of libp2p.
-
-{{< youtube Xw-5cRSs85M>}}
-
-{{< embed src="https://docs.google.com/presentation/d/e/2PACX-1vSBFLQibkm_YWUi0sIaY7CLLd4PMpPk0kjgE1nt5XPBuHwhTU0owdCP44nv5OzBmoDAOIwcy4Ngx0AV/embed?start=false&loop=false&delayms=3000" frameborder="0" width="100%" height="500" allowfullscreen="true" mozallowfullscreen="true" webkitallowfullscreen="true" >}}
-Introduction to libp2p (3/9/23)
-
 ## libp2p Shallow Dive
 
 This Shallow Dive explores the core topics of libp2p including transports, multiplexers, peer routing, implementations, and more!

content/en/curriculum/libp2p/pubsub/index.md

@@ -5,7 +5,7 @@ draft: false
 menu:
     curriculum:
         parent: "curriculum-libp2p"
-weight: 330
+weight: 60
 category: lecture
 objectives:
   show: true
@@ -42,7 +42,7 @@ FloodSub is simple, reliable, and highly resistant to malicious actors and censo
 
 ## Gossipsub
 
-The main goal of Gossipsub is to reduce the bandwith used in delivering messages.
+The main goal of Gossipsub is to reduce the bandwidth used in delivering messages.
 In the Gossipsub, peers can connect by setting up a _full-message connection_ or a _metadata-only connection_.
 Full-message peers exchange all the information about the message; metadata-only peers exchange only data identifying the message, but not the full message itself.
 
@@ -57,14 +57,14 @@ The number of _full-message_ peers that a node is connected to, depends on a par
 You can get more information about PubSub in the [libp2p documentation](https://docs.libp2p.io/concepts/publish-subscribe/) and the in the following videos, which extensively cover the Gossipsub protocol.
 
 ## Tutorial: Publish Subscribe (Pubsub) with IPFS & libp2p
-In this tutorial video, you will see how you can use the publish-subscribe functionality (using the libp2p Gossipsub routing algorithm) with an IPFS node.  Follow along to start an IPFS node with pubsub enabled, and send and recieve messages.
+In this tutorial video, you will see how you can use the publish-subscribe functionality (using the libp2p Gossipsub routing algorithm) with an IPFS node.  Follow along to start an IPFS node with pubsub enabled, and send and receive messages.
 
 {{< youtube 9pUqOhORsYI >}}
 
 **Resources:**
 * [Blog with Pubsub instructions](https://bitly.protocol.ai/pubsub-blog)
 * [Other Pubsub Options](https://bitly.protocol.ai/pusub-flags)
-* [lipbp2p Docs – Publish/Subscribe](https://docs.libp2p.io/concepts/publish-subscribe/)
+* [libp2p Docs – Publish/Subscribe](https://docs.libp2p.io/concepts/publish-subscribe/)
 
 
 ## Expand Your Knowledge

cspell.json

@@ -16,6 +16,7 @@
         "Bitswap",
         "Buterin",
         "Cailliau",
+        "celestia",
         "Chainsafe",
         "chunker",
         "Cloudbreak",
@@ -28,31 +29,41 @@
         "Cypherpunks",
         "devgrants",
         "Devnet",
+        "dialable",
+        "dialbacks",
         "Doks",
         "Drand",
+        "elrond",
+        "endtab",
+        "endtabs",
         "Errorf",
         "Esturary",
         "Filecoin",
         "FIPs",
         "Fisch",
         "Fleek",
+        "Floodsub",
         "Freepik",
         "Gailly",
         "Gitbook",
+        "gossipsub",
         "Haire",
         "HAMT",
         "Hashcash",
         "Immutabilty",
         "incentivized",
         "incentivizes",
         "incentivizing",
+        "Inden",
         "IPFS",
         "IPLD",
         "IPNS",
         "João",
         "Kademlia",
         "Keepkey",
         "keypair",
+        "Kreiger",
+        "Kripalani",
         "kubo",
         "Kusama",
         "Labbers",
@@ -65,16 +76,26 @@
         "markdownify",
         "mediary",
         "Merkle",
+        "minaprotocol",
         "momack",
+        "Mplex",
+        "Multiaddr",
+        "multiaddress",
+        "Multiaddresses",
         "Multiformat",
         "Multiformats",
         "multihash",
+        "multihashes",
         "Multipass",
         "Multisigs",
+        "multistream",
+        "Muxers",
         "Nakamoto",
         "Namecoin",
         "netops",
         "networkʼs",
+        "nodeutils",
+        "onflow",
         "onramps",
         "Palo",
         "parachain",
@@ -88,8 +109,12 @@
         "Polymarket",
         "Pooja",
         "Powergate",
+        "println",
         "protobuf",
         "Protoschool",
+        "Prysmaticlabs",
+        "QUIC",
+        "Raúl",
         "retrievability",
         "Rijndael",
         "Rollups",
@@ -123,6 +148,7 @@
         "Vagg",
         "Vitalik",
         "waitlist",
+        "websockets",
         "whistleblower",
         "Zenground",
         "Zhang",
@@ -135,6 +161,7 @@
         "Bondy",
         "Bpfs",
         "CVHM",
+        "FINDE",
         "Gbbg",
         "Gkginqktrq",
         "HQJE",
@@ -144,8 +171,10 @@
         "Lbqqvo",
         "Nzrz",
         "Ocmv",
+        "Oswx",
         "Ponv",
         "Pyfrt",
+        "Rvro",
         "Sbpd",
         "Schmahmann",
         "Tzfcq",
@@ -161,10 +190,12 @@
         "filesize",
         "killall",
         "lfuat",
+        "medata",
         "mozallowfullscreen",
         "ojxfb",
         "qldyrv",
         "rschanger",
+        "uftr",
         "webkitallowfullscreen"
     ],
     "import": []