From 746524928cbcfa7e9051b6f7f9ea17bb6d16c04a Mon Sep 17 00:00:00 2001 From: Vladimir Panteleev Date: Wed, 12 Jul 2023 17:04:32 +0000 Subject: [PATCH] Fix grammar in client-server-api intro (#1597) --- changelogs/client_server/newsfragments/1597.clarification | 1 + content/client-server-api/_index.md | 2 +- 2 files changed, 2 insertions(+), 1 deletion(-) create mode 100644 changelogs/client_server/newsfragments/1597.clarification diff --git a/changelogs/client_server/newsfragments/1597.clarification b/changelogs/client_server/newsfragments/1597.clarification new file mode 100644 index 00000000..3ccb2333 --- /dev/null +++ b/changelogs/client_server/newsfragments/1597.clarification @@ -0,0 +1 @@ +Fix various typos throughout the specification. diff --git a/content/client-server-api/_index.md b/content/client-server-api/_index.md index 8ebe8f71..0e7e8473 100644 --- a/content/client-server-api/_index.md +++ b/content/client-server-api/_index.md @@ -62,7 +62,7 @@ error message e.g. `M_FORBIDDEN`. Error codes should have their namespace first in ALL CAPS, followed by a single `_`. For example, if there was a custom namespace `com.mydomain.here`, and a `FORBIDDEN` code, the error code should look like `COM.MYDOMAIN.HERE_FORBIDDEN`. Error codes defined by this -specification should start `M_`. +specification should start with `M_`. Some `errcode`s define additional keys which should be present in the error response object, but the keys `error` and `errcode` MUST always be present.