chore: Adjust READMEs (#33)

* envoy-proto-collect: adjust `README` formatting

* examples: adjust `README`

Format, use inline links, add 'Quick Templates' section.

Author: flemosr

envoy-proto-collect/README.md

@@ -1,30 +1,27 @@
 # Envoy Proto Collect
 
-This crate is a tool used to collect selected proto files from the repos
-contained in the `submodules` directory, adding said files to the repo's
-`envoy-types/proto` directory.
+This crate is a tool used to collect selected proto files from the repos contained in the
+`submodules` directory, adding said files to the repo's `envoy-types/proto` directory.
 
-Besides that, `Apache-2.0` declarations are added to the top of the proto files
-lacking them.
+Besides that, `Apache-2.0` declarations are added to the top of the proto files lacking them.
 
 ## Run the Proto Collection Tool
 
-First, delete the contents of the repo's `envoy-types/proto` directory, to
-ensure that only the protos that were just collected are present in the
-directory by the end of the process.
+First, delete the contents of the repo's `envoy-types/proto` directory, to ensure that only the
+protos that were just collected are present in the directory by the end of the process.
 
 Then, run the tool:
 
 ```bash
 $ cargo run --bin collect-protos
 ```
 
-The compilation of the protos can be achieved by running the `bootstrap` test
-of the `envoy-types` crate. This can be done by simply running:
+The compilation of the protos can be achieved by running the `bootstrap` test of the `envoy-types`
+crate. This can be done by simply running:
 
 ```bash
 $ cargo test bootstrap
 ```
 
-On the repo's root directory. If `git` detects any changes in the resulting
-generated files, the test will fail.
+On the repo's root directory. If `git` detects any changes in the resulting generated files, the
+test will fail.

examples/README.md

@@ -1,11 +1,20 @@
 # Examples
 
+## Quick Templates
+
+Direct source code links for quick reference:
+
+| Category | Raw Source |
+|----------|------------|
+| **ExtAuthz Server Basic** | [authorization_server_basic.rs](https://raw.githubusercontent.com/flemosr/envoy-types/refs/heads/main/examples/src/ext_authz/authorization_server_basic.rs) |
+| **ExtAuthz Server Full** | [authorization_server_full.rs](https://raw.githubusercontent.com/flemosr/envoy-types/refs/heads/main/examples/src/ext_authz/authorization_server_full.rs) |
+| **ExtAuthz Server PB Only** | [authorization_server_pb_only.rs](https://raw.githubusercontent.com/flemosr/envoy-types/refs/heads/main/examples/src/ext_authz/authorization_server_pb_only.rs) |
+
 ## Envoy's ExtAuthz gRPC Authorization Server
 
 There are three examples showing how to implement an
-[Envoy External Authorization] gRPC Server written in Rust, with [`tonic`].
-
-[Envoy External Authorization]: https://www.envoyproxy.io/docs/envoy/latest/configuration/http/http_filters/ext_authz_filter
+[Envoy External Authorization](https://www.envoyproxy.io/docs/envoy/latest/configuration/http/http_filters/ext_authz_filter)
+gRPC Server written in Rust, with [`tonic`](https://github.com/hyperium/tonic).
 
 A bare-bones implementation:
 
@@ -27,9 +36,5 @@ $ cargo run --example authorization-server-pb-only
 ```
 
 For more complete examples, including the connection to an actual `envoy`
-container, check the [envoy-extauthz-rust] and [envoy-extauthz-rust-rate-limit]
+container, check the [envoy-extauthz-rust](https://github.com/flemosr/envoy-extauthz-rust) and [envoy-extauthz-rust-rate-limit](https://github.com/flemosr/envoy-extauthz-rust-rate-limit)
 repositories.
-
-[envoy-extauthz-rust]: https://github.com/flemosr/envoy-extauthz-rust
-[envoy-extauthz-rust-rate-limit]: https://github.com/flemosr/envoy-extauthz-rust-rate-limit
-[`tonic`]: https://github.com/hyperium/tonic