From ea4719793041dfccdef9071edb5ad8526536619b Mon Sep 17 00:00:00 2001 From: Saiprakash Shet Date: Thu, 16 Feb 2023 02:39:29 +0530 Subject: [PATCH] Update spelling in s2s authorization (#1431) * Issue #1231/Update spelling in s2s authorization * Update spelling in s2s authorization. * Apply suggestions from code review --------- Co-authored-by: Travis Ralston --- changelogs/server_server/newsfragments/1431.clarification | 1 + content/server-server-api.md | 2 +- 2 files changed, 2 insertions(+), 1 deletion(-) create mode 100644 changelogs/server_server/newsfragments/1431.clarification diff --git a/changelogs/server_server/newsfragments/1431.clarification b/changelogs/server_server/newsfragments/1431.clarification new file mode 100644 index 00000000..3ccb2333 --- /dev/null +++ b/changelogs/server_server/newsfragments/1431.clarification @@ -0,0 +1 @@ +Fix various typos throughout the specification. diff --git a/content/server-server-api.md b/content/server-server-api.md index 34f9f5b5..bcf0db4e 100644 --- a/content/server-server-api.md +++ b/content/server-server-api.md @@ -350,7 +350,7 @@ The authorization parameters to include are: - `origin`: the server name of the sending server. This is the same as the `origin` field from JSON described in step 1. - `destination`: {{< added-in v="1.3" >}} the server name of the receiving - sender. This is the same as the `destination` field from the JSON described + server. This is the same as the `destination` field from the JSON described in step 1. For compatibility with older servers, recipients should accept requests without this parameter, but MUST always send it. If this property is included, but the value does not match the receiving server's name, the