fixed typos (#433)

Signed-off-by: Nir Rozenbaum <[email protected]>

Author: nirrozenbaum

docs/proposals/003-model-server-protocol/README.md

@@ -43,7 +43,7 @@ The model server MUST expose the following LoRA adapter metrics via the same Pro
 * Metric value: The last updated timestamp (so the EPP can find the latest).
 * Metric labels: 
   * `max_lora`: The maximum number of adapters that can be loaded to GPU memory to serve a batch.
-  Requests will be queued if the model server has reached MaxActiveAdapter and canno load the
+  Requests will be queued if the model server has reached MaxActiveAdapter and cannot load the
   requested adapter. Example: `"max_lora": "8"`.
   * `running_lora_adapters`: A comma separated list of adapters that are currently loaded in GPU
     memory and ready to serve requests. Example: `"running_lora_adapters": "adapter1, adapter2"`

docs/proposals/004-endpoint-picker-protocol/README.md

@@ -7,7 +7,7 @@ found [here](../../../pkg/epp/).
 This doc defines the protocol between the EPP and the proxy (e.g, Envoy).
 
 The EPP MUST implement the Envoy
-[external processing service](https://www.envoyproxy.io/docs/envoy/latest/api-v3/service/ext_proc/v3/external_processor)protocol.
+[external processing service](https://www.envoyproxy.io/docs/envoy/latest/api-v3/service/ext_proc/v3/external_processor) protocol.
 
 For each HTTP request, the EPP MUST communicate to the proxy the picked model server endpoint via: