From 8e630fac8f6f85bdc62bfb3a6f5b2dac5de3c29c Mon Sep 17 00:00:00 2001 From: bitfl0wer Date: Tue, 7 Jan 2025 14:58:42 +0100 Subject: [PATCH] fix typos --- docs/Protocol Specifications/core.md | 6 +++--- 1 file changed, 3 insertions(+), 3 deletions(-) diff --git a/docs/Protocol Specifications/core.md b/docs/Protocol Specifications/core.md index e91cbc44..acccdb89 100644 --- a/docs/Protocol Specifications/core.md +++ b/docs/Protocol Specifications/core.md @@ -1379,12 +1379,12 @@ references to it. One way to ensure the uniqueness of the identifier is to use a resource itself. Combining this has with a cryptographically strong nonce, then hashing the result of concatenating the nonce and the hash of the resource should yield a unique identifier. -The API route for resource addressing with relative roots is formatted as follows: +The URI for resource addressing with relative roots is formatted as follows: `/.p2/core/resource/` -The API route for resource addressing with relative roots is documented more thoroughly in the API -documentation. +The API routes for resource addressing with relative roots are documented more thoroughly in the [API +documentation](https://apidocs.polyproto.org). Servers with no need for resource addressing with relative roots can select to not implement this feature. Servers not implementing this feature should return a `404 Not Found` status code when