From 6f53e43238920dda596bfbf21edc28f524ef8f53 Mon Sep 17 00:00:00 2001 From: Michael Quigley Date: Mon, 26 Jun 2023 12:48:20 -0400 Subject: [PATCH] tweaks --- docs/core-features/sharing-reserved.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/docs/core-features/sharing-reserved.md b/docs/core-features/sharing-reserved.md index 04f8a145..ee28c9c1 100644 --- a/docs/core-features/sharing-reserved.md +++ b/docs/core-features/sharing-reserved.md @@ -3,7 +3,7 @@ sidebar_position: 10 --- # Reserved Shares -By default a `public` or `private` share is allocated a _share token_ when you run the `zrok share` command. The `zrok share` command is the bridge between your local environment and the users you are sharing with. When you terminate the `zrok share`, the bridge is eliminated and the _share token_ is deleted. If you run `zrok share` again, you will be allocated a brand new _share token_. +By default a `public` or `private` share is assigned a _share token_ when you create a share using the `zrok share` command. The `zrok share` command is the bridge between your local environment and the users you are sharing with. When you terminate the `zrok share`, the bridge is eliminated and the _share token_ is deleted. If you run `zrok share` again, you will be allocated a brand new _share token_. You can use a `reserved` share to persist your _share token_ across multiple runs of the `zrok share` bridge. When you use a `reserved` share, the share token will not be deleted between multiple runs of `zrok share`.