callout p2p and openziti in the private sharing

docs/core-features/sharing-private.md

@@ -7,6 +7,8 @@ sidebar_position: 0
 shared through a __privately__ available endpoint. Sharing a resource with `private` is __a differentiating__
 feature of `zrok`.
 
+# Peer to Peer
+
 ![zrok_public_share](../images/zrok_private_share.png)
 
 A `private` share will require `zrok` to access the share and will also require a special shared 
@@ -14,8 +16,10 @@ secret token. This access token, combined with the `zrok access` command will be
 
 Sharing something with `private` is similar to sharing something publicly. The main difference is
 obvious, the shared resource is `private` and the share is __not__ open to the public. With `zrok`, you
-can share resources on a private network without needing to expose the service to the internet, not 
-even through an obfuscated, difficult to guess url. There will be no attack surface available to the public.
+can share resources on a private network without needing to expose the service to the internet. The share is not 
+through an obfuscated, difficult to guess url. Instead the sharing is accomplished using a secure, zero trust overlay
+network provided by [OpenZiti](https://openziti.io). With this private, peer to peer sharing model, there will
+never an attack surface available to the open internet.
 
 The shared resource can be a development web server to share with friends and colleagues or perhaps,
 it could be a webhook from a server running in the cloud which has `zrok` running and has been instructed

docs/core-features/sharing-public.md

@@ -6,6 +6,8 @@ sidebar_position: 10
 `zrok` was built to share and access digital resources. a `public` share allows something to be shared through 
 a publicly available endpoint.
 
+## Public Sharing
+
 ![zrok_public_share](../images/zrok_public_share.png)
 
 Sharing something with `public` is useful when the person or service accessing the thing being shared doesn't