Update documentation

examples/cpp/adhoc.cpp

@@ -35,10 +35,10 @@
  *   root server has passed contact information to both peers that a direct connection will be
  *   established. Therefore, it is required that multiple connection attempts be undertaken
  *   when initially communicating with a peer. After a transport-triggered link is
- *   established libzt will inform you via ZTS_EVENT_PEER_P2P for a specific peer ID. No
+ *   established libzt will inform you via ZTS_EVENT_PEER_DIRECT for a specific peer ID. No
  *   action is required on your part for this callback event.
  *
- *   Note: In these initial moments before ZTS_EVENT_PEER_P2P has been received for a
+ *   Note: In these initial moments before ZTS_EVENT_PEER_DIRECT has been received for a
  *         specific peer, traffic may be slow, jittery and there may be high packet loss.
  *         This will subside within a couple of seconds.
  *

examples/cpp/client.cpp

@@ -127,10 +127,10 @@ void myZeroTierEventCallback(void *msgPtr)
  *   root server has passed contact information to both peers that a direct connection will be
  *   established. Therefore, it is required that multiple connection attempts be undertaken
  *   when initially communicating with a peer. After a transport-triggered link is
- *   established libzt will inform you via ZTS_EVENT_PEER_P2P for a specific peer ID. No
+ *   established libzt will inform you via ZTS_EVENT_PEER_DIRECT for a specific peer ID. No
  *   action is required on your part for this callback event.
  *
- *   Note: In these initial moments before ZTS_EVENT_PEER_P2P has been received for a
+ *   Note: In these initial moments before ZTS_EVENT_PEER_DIRECT has been received for a
  *         specific peer, traffic may be slow, jittery and there may be high packet loss.
  *         This will subside within a couple of seconds.
  *

examples/cpp/comprehensive.cpp

@@ -35,10 +35,10 @@
  *   root server has passed contact information to both peers that a direct connection will be
  *   established. Therefore, it is required that multiple connection attempts be undertaken
  *   when initially communicating with a peer. After a transport-triggered link is
- *   established libzt will inform you via ZTS_EVENT_PEER_P2P for a specific peer ID. No
+ *   established libzt will inform you via ZTS_EVENT_PEER_DIRECT for a specific peer ID. No
  *   action is required on your part for this callback event.
  *
- *   Note: In these initial moments before ZTS_EVENT_PEER_P2P has been received for a
+ *   Note: In these initial moments before ZTS_EVENT_PEER_DIRECT has been received for a
  *         specific peer, traffic may be slow, jittery and there may be high packet loss.
  *         This will subside within a couple of seconds.
  *

examples/cpp/earthtest.cpp

@@ -35,10 +35,10 @@
  *   root server has passed contact information to both peers that a direct connection will be
  *   established. Therefore, it is required that multiple connection attempts be undertaken
  *   when initially communicating with a peer. After a transport-triggered link is
- *   established libzt will inform you via ZTS_EVENT_PEER_P2P for a specific peer ID. No
+ *   established libzt will inform you via ZTS_EVENT_PEER_DIRECT for a specific peer ID. No
  *   action is required on your part for this callback event.
  *
- *   Note: In these initial moments before ZTS_EVENT_PEER_P2P has been received for a
+ *   Note: In these initial moments before ZTS_EVENT_PEER_DIRECT has been received for a
  *         specific peer, traffic may be slow, jittery and there may be high packet loss.
  *         This will subside within a couple of seconds.
  *

examples/cpp/server.cpp

@@ -127,10 +127,10 @@ void myZeroTierEventCallback(void *msgPtr)
  *   root server has passed contact information to both peers that a direct connection will be
  *   established. Therefore, it is required that multiple connection attempts be undertaken
  *   when initially communicating with a peer. After a transport-triggered link is
- *   established libzt will inform you via ZTS_EVENT_PEER_P2P for a specific peer ID. No
+ *   established libzt will inform you via ZTS_EVENT_PEER_DIRECT for a specific peer ID. No
  *   action is required on your part for this callback event.
  *
- *   Note: In these initial moments before ZTS_EVENT_PEER_P2P has been received for a
+ *   Note: In these initial moments before ZTS_EVENT_PEER_DIRECT has been received for a
  *         specific peer, traffic may be slow, jittery and there may be high packet loss.
  *         This will subside within a couple of seconds.
  *

examples/objective-c/adhoc.m

@@ -44,10 +44,10 @@
  *   root server has passed contact information to both peers that a direct connection will be
  *   established. Therefore, it is required that multiple connection attempts be undertaken
  *   when initially communicating with a peer. After a transport-triggered link is
- *   established libzt will inform you via ZTS_EVENT_PEER_P2P for a specific peer ID. No
+ *   established libzt will inform you via ZTS_EVENT_PEER_DIRECT for a specific peer ID. No
  *   action is required on your part for this callback event.
  *
- *   Note: In these initial moments before ZTS_EVENT_PEER_P2P has been received for a
+ *   Note: In these initial moments before ZTS_EVENT_PEER_DIRECT has been received for a
  *         specific peer, traffic may be slow, jittery and there may be high packet loss.
  *         This will subside within a couple of seconds.
  *

examples/swift/main.swift

@@ -40,10 +40,10 @@ import Foundation
  *   root server has passed contact information to both peers that a direct connection will be
  *   established. Therefore, it is required that multiple connection attempts be undertaken
  *   when initially communicating with a peer. After a transport-triggered link is
- *   established libzt will inform you via ZTS_EVENT_PEER_P2P for a specific peer ID. No
+ *   established libzt will inform you via ZTS_EVENT_PEER_DIRECT for a specific peer ID. No
  *   action is required on your part for this callback event.
  *
- *   Note: In these initial moments before ZTS_EVENT_PEER_P2P has been received for a
+ *   Note: In these initial moments before ZTS_EVENT_PEER_DIRECT has been received for a
  *         specific peer, traffic may be slow, jittery and there may be high packet loss.
  *         This will subside within a couple of seconds.
  *
@@ -200,8 +200,8 @@ let myZeroTierEventCallback : @convention(c) (UnsafeMutableRawPointer?) -> Void
 			ipstr, msg.addr->nwid)
 		*/
 	// Peer events
-	case ZTS_EVENT_PEER_P2P:
-		print("ZTS_EVENT_PEER_P2P --- node=%llx\n", msg.peer->address)
+	case ZTS_EVENT_PEER_DIRECT:
+		print("ZTS_EVENT_PEER_DIRECT --- node=%llx\n", msg.peer->address)
 	case ZTS_EVENT_PEER_RELAY:
 		print("ZTS_EVENT_PEER_RELAY --- node=%llx\n", msg.peer->address)