sdk in its own dir

documentation/new_docs/pages/sdk/_meta.json

@@ -1,4 +1,4 @@
 {
-  "typescript": "Typescript",
-  "rust": "Rust"
+  "rust": "Rust SDK",
+  "typescript": "Typescript SDK"
 }

documentation/new_docs/pages/sdk/rust/_meta.json

@@ -1,6 +1,5 @@
 {
   "index": "Introduction",
-  "concepts": "Core Concepts",
   "examples": "Basic Examples",
   "message-helpers": "Message Helpers",
   "message-types": "Message Types",

documentation/new_docs/pages/sdk/rust/concepts/_meta.json

@@ -1,5 +0,0 @@
-{
-  "overview": "Overview",
-  "messages": "Message Based Paradigm",
-  "abstractions": "Connection Abstractions"
-}

documentation/new_docs/pages/sdk/rust/examples/builders.md

@@ -0,0 +1,3 @@
+# Builder Patterns
+
+Since there are two ways of creating an SDK client - ephemeral and with-storage - then there are two ways of applying the Builder Pattern to client creation.

documentation/new_docs/pages/sdk/rust/examples/builders/builder.md

@@ -1,5 +1,7 @@
 # Mixnet Client Builder
 
+You can spin up an ephemeral client like so. This client will not have a persistent identity and its keys will be dropped on restart. Since there is currently no way of reconnecting a client that has been disconnected after use, then treat disconnecting a client the same as dropping its keys entirely.
+
 > You can find this code [here](https://github.com/nymtech/nym/blob/master/sdk/rust/nym-sdk/examples/builder.rs).
 
 ```rust

documentation/new_docs/pages/sdk/rust/examples/custom-topology/_meta.json

@@ -1,5 +1,4 @@
 {
-  "custom-network": "Different Options",
   "custom-provider": "Custom Topology Provider",
   "manual-topology": "Manually Overwrite Topology"
 }