Rephrase and use examples

Author: MarcoPolo

protocols/httppath.md

@@ -1,32 +1,26 @@
 # `httppath`
 
 This protocol encodes an HTTP Path to a resource. In the string representation,
-characters in the reserved set are percent-encoded ( "/" becomes "%2F").
-Percent-encoding itself is defined by [RFC 3986 Section
-2.1](https://datatracker.ietf.org/doc/html/rfc3986#section-2.1). In the binary representation, no escaping is needed as the value is length prefixed.
-
-To ease implementation and benefit from reusing existing percent-encoding logic
-present in many environments (Go's
-[url.PathEscape](https://pkg.go.dev/net/[email protected]#PathEscape); JS's
-[encodeURIComponent](http://developer.mozilla.org/en-US/docs/Web/JavaScript/Reference/Global_Objects/encodeURIComponent);
-and Rust's [many
-crates](https://crates.io/search?q=percent%20encode&sort=downloads)), it is
-acceptable to encode more characters than the reserved set. While it's not
-necessary to encode a space " " as %20, it's is acceptable to do so.
+the path is encoded in a way consistent with a single URI Path segment per [RFC 3986 Section
+3.3](https://datatracker.ietf.org/doc/html/rfc3986#autoid-23). Specifically
+following the grammar of a single `segment-nz`. In the binary
+representation, no encoding is needed as the value is length prefixed.
 
 When comparing multiaddrs, implementations should compare their binary
 representation to avoid ambiguities over which characters were escaped.
 
-## Reserved Characters
+## Examples
 
-| Character | Reason                                                                                               |
-| --------- | ---------------------------------------------------------------------------------------------------- |
-| `/`       | Multiaddr component separator                                                                        |
-| `%`       | Percent encoding indicator                                                                           |
-| `?`       | Marks the end of an HTTP path                                                                        |
-| `#`       | Reserved gen-delim character by [rfc3986](https://datatracker.ietf.org/doc/html/rfc3986#section-2.2) |
-| `[`       | Reserved gen-delim character by [rfc3986](https://datatracker.ietf.org/doc/html/rfc3986#section-2.2) |
-| `]`       | Reserved gen-delim character by [rfc3986](https://datatracker.ietf.org/doc/html/rfc3986#section-2.2) |
+The following is a table of examples converting some common HTTP paths to their Multiaddr string form.
+
+| HTTP Path       | Multiaddr string form            |
+| --------------- | -------------------------------- |
+| /               | n/a. This is implied.            |
+| /user           | `/httppath/user`                 |
+| /api/v0/login   | `/httppath/api%2Fv0%2Flogin`     |
+| /tmp/foo/../bar | `/httppath/tmp%2Ffoo%2F..%2Fbar` |
+| a%20space       | `/httppath/a%2520space`          |
+| a%2Fslash       | `/httppath/a%252Fslash`          |
 
 ## Usage