docs navigation and global transport docs

docs/BUFFERS.md

@@ -14,4 +14,7 @@ Above, the `SoundToPlay` buffer which is being referenced by the `{groove~}` obj
 
 - The data for this `WaveAsset` is all loaded in RAM uncompressed. This might become an issue if you are working with large files. Also, each pin gets represents a unique copy of the data, so if you're mapping the same `WaveAsset` to two different pins, you get that data loaded in memory two times.
 
-- Finally, note that we don't currently copy over the samples you may have loaded in your RNBO patch with `{buffer foo @file bar.aif}`. This enhancement is being tracked on [issue #29](https://github.com/Cycling74/RNBOMetasound/issues/29).
+- Finally, note that we don't currently copy over the samples you may have loaded in your RNBO patch with `{buffer foo @file bar.aif}`. This enhancement is being tracked on [issue #29](https://github.com/Cycling74/RNBOMetasound/issues/29).
+
+- Back to [Node I/O](NODE_IO.md)
+- Next: [MIDI](MIDI.md)

docs/MIDI.md

@@ -16,4 +16,7 @@ The `Make Note` node is very similar to RNBO's `{makenote}` object, but as a Met
 
 Your RNBO patchers (and thus nodes) can be polyphonic. In order to send multiple MIDI note-on messages into a node at the same time, for example, to play a chord, you can use the `MIDI Merge` nodes, which take several MIDI type inputs and output them along a single patch cord. 
 
-The `MIDI Merge` nodes have several versions, which you can select from depending on how many MIDI sources you'd like to merge. 
+The `MIDI Merge` nodes have several versions, which you can select from depending on how many MIDI sources you'd like to merge. 
+
+- Back to [Buffers and Wave Assets](BUFFERS.md)
+- Next: [Transport - Global and Local](TRANSPORT.md)

docs/NODE_IO.md

@@ -38,4 +38,7 @@ At present, `@enum` parameters are transformed into `Int` type pin in the MS nod
 
 ### Other Pin Types
 
-For more information, see the [Buffers](BUFFERS.md), [MIDI](MIDI.md), and [Transport](TRANSPORT.md) articles.
+For more information, see the [Buffers](BUFFERS.md), [MIDI](MIDI.md), and [Transport](TRANSPORT.md) articles.
+
+- Back to [Table Of Contents](README.md/#documentation-table-of-contents)
+- Next: [Buffers and Wave Assets](BUFFERS.md)

docs/TRANSPORT.md

@@ -6,4 +6,16 @@ The RNBO MetaSound node has an input pin that takes the `Transport` type. The `T
 
 ## Global Transport
 
-More documentation of this feature coming soon.
+RNBO's Global Transport provides a solution for synchronizing various running MetaSounds. Any instances of the `Global Transport` node, as opposed to the `Transport` node, share state across active MetaSounds. 
+
+![global-transport](img/global-transport.png)
+
+There should only ever be one active instance of a `Global Transport Control` node running in your project. Using this node, you can set the `BPM`, running state, and the `Numerator` and `Denominator` of the time signature for RNBO's transport. 
+
+Once you've set these input parameters, you can apply, or `Latch` those values to the global transport with a trigger sent to the `Latch` input pin.
+
+Additionally, you can set a `BeatTime`, defined in quarter notes since the start of the transport (beat "one"), and then `Seek` to that location by sending a trigger to the `Seek` input pin.
+
+
+- Back to [MIDI](MIDI.md)
+- Return to [Table Of Contents](README.md/#documentation-table-of-contents)