From 585551104639ef51a1c09085660fb8689aeae36a Mon Sep 17 00:00:00 2001 From: Lukas Herman Date: Wed, 22 Jan 2025 21:12:12 -0500 Subject: [PATCH] Update README.md --- examples/README.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/examples/README.md b/examples/README.md index f2e3bb0..5799cb7 100644 --- a/examples/README.md +++ b/examples/README.md @@ -47,7 +47,7 @@ Now you should have two tokens. You can use the tokens to connect the two peers | `allow-policy`| Defines which peer(s) this peer is allowed to connect to. Default: `"*:*"` (connect to any other peer)[^1]. [More info](https://jsr.io/@pulsebeam/server/doc/~/PeerPolicy) | | `create-token`| Generates a token[^2][^3] based on the provided inputs/defaults. | -[^1]: Even with the `\"*:*\"` allow-policy, peers can only connect to other peers within the scope of your ``. +[^1]: Even with the `"*:*"` allow-policy, peers can only connect to other peers within the scope of your ``. [^2]: Provide the CLI-generated token to your client's to allow them to talk to PulseBeam signaling servers and make connections with each other.