From 4f67f5c9990c4cd6594d453a5404af9cd1fd5951 Mon Sep 17 00:00:00 2001 From: sgmoore Date: Fri, 16 Dec 2022 22:35:56 -0800 Subject: [PATCH] Minor grammar and spelling fixes Minor grammar fix at line 48. Minor spelling fix at line 56. --- 05.md | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) diff --git a/05.md b/05.md index 8aaa4d76..4c1ebc58 100644 --- a/05.md +++ b/05.md @@ -45,7 +45,7 @@ A client can also use this to allow users to search other profiles. If a client ### Showing just the domain as an identifier -Clients may treat the identifier `_@domain` as the "root" identifier, and choose to display it as just the ``. For example, if Bob owns `bob.com`, he may not want an identifier like `bob@bob.com` as that is redundant. Instead Bob can use the identifier `_@bob.com` and expect Nostr clients to show and treat that as just `bob.com` for all purposes. +Clients may treat the identifier `_@domain` as the "root" identifier, and choose to display it as just the ``. For example, if Bob owns `bob.com`, he may not want an identifier like `bob@bob.com` as that is redundant. Instead, Bob can use the identifier `_@bob.com` and expect Nostr clients to show and treat that as just `bob.com` for all purposes. ### Reasoning for the `/.well-known/nostr.json?name=` format @@ -53,7 +53,7 @@ By adding the `` as a query string instead of as part of the path th ### Allowing access from JavaScript apps -JavaScript Nostr apps may be restricted by browser [CORS][] policies that prevent them from accesing `/.well-known/nostr.json` on the user's domain. When CORS prevents JS from loading a resource, the JS program sees it as a network failure identical to the resource not existing, so it is not possible for a pure-JS app to tell the user for certain that the failure was caused by a CORS issue. JS Nostr apps that see network failures requesting `/.well-known/nostr.json` files may want to recommend to users that they check the CORS policy of their servers, e.g.: +JavaScript Nostr apps may be restricted by browser [CORS][] policies that prevent them from accessing `/.well-known/nostr.json` on the user's domain. When CORS prevents JS from loading a resource, the JS program sees it as a network failure identical to the resource not existing, so it is not possible for a pure-JS app to tell the user for certain that the failure was caused by a CORS issue. JS Nostr apps that see network failures requesting `/.well-known/nostr.json` files may want to recommend to users that they check the CORS policy of their servers, e.g.: ```bash $ curl -sI https://example.com/.well-known/nostr.json?name=bob | grep ^Access-Control