Update README.md

Author: lherman-cs

examples/README.md

@@ -44,7 +44,7 @@ Now you should have two tokens. You can use the tokens to connect the two peers
 | `peer-id`     | ID for the peer this token is intended to be used by. [More info](https://jsr.io/@pulsebeam/server/doc/~/PeerClaims#constructor_0) |
 | `group-id`    | ID for the group the peer is in, scoped to your application. [More info](https://jsr.io/@pulsebeam/server/doc/~/PeerClaims#constructor_0) |
 | `duration`    | Duration in seconds TTL before token expiration.                                                          |
-| `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) |
+| `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 `<API_KEY>`.