Update mkdocs

docs/async-await.md

@@ -52,7 +52,7 @@ static void Main(string[] args)
 ```
 
 NetMQRuntime is a wrapper over NetMQPoller, when calling an async function the socket is automatically added to the internal poller.
-NetMQRuntime is also a NetMQScheduler and SyncrhonizationContext, so any awaited function is continuing on the runtime's thread.
+NetMQRuntime is also a NetMQScheduler and SynchronizationContext, so any awaited function is continuing on the runtime's thread.
 
 NetMQSocket should still be used only within one thread.
 

docs/poller.md

@@ -59,7 +59,7 @@ For ZeroMQ/NetMQ to give great performance, some restrictions exist on how we ca
 
 For example, consider socket A with a service loop in thread A, and socket B with a service loop in thread B. It would be invalid to receive a message from socket A (on thread A) and then attempt to send it on socket B. The socket is not threadsafe, and so attempts to use is simultaneously from threads A and B would cause errors.
 
-In fact the pattern described here is known as a [proxy](proxy.md), and one is built into NetMQ. At this point you may not be surprised to learn that it is powered by a `NetMQPoller`.
+In fact the pattern described here is known as a proxy, and one is built into NetMQ. At this point you may not be surprised to learn that it is powered by a `NetMQPoller`.
 
 ## Example: ReceiveReady
 

mkdocs.yml

@@ -1,6 +1,6 @@
 site_name: NetMQ
 
-pages:
+nav:
 - Home: index.md
 - Introduction: introduction.md
 - Concepts:
@@ -16,6 +16,7 @@ pages:
   - Timer: timer.md
   - Queue: queue.md
   - Proactor: proactor.md
+  - Devices: devices.md
 - Patterns:
   - Request-Response: request-response.md
   - Pub-Sub: pub-sub.md