From 23f1677422b0f2762944a7e4f1102f141d26cc84 Mon Sep 17 00:00:00 2001 From: Gary dos Santos Date: Tue, 1 Sep 2026 10:14:38 +0200 Subject: [PATCH] fix: corrected typos in connection-coordinator - Corrected identfiier to identifier - Corrected responsiblity to responsibility --- connection-coordinator/docs/Protocols.md | 2 +- connection-coordinator/schemas/connection.yaml | 2 +- 2 files changed, 2 insertions(+), 2 deletions(-) diff --git a/connection-coordinator/docs/Protocols.md b/connection-coordinator/docs/Protocols.md index b48fc37..3752273 100644 --- a/connection-coordinator/docs/Protocols.md +++ b/connection-coordinator/docs/Protocols.md @@ -228,7 +228,7 @@ the customer out of band to the partner provider. The remote provider * The desired bandwidth is in fact still available * That the listed account identifier in the **ActivationKey** is the same as the authenticated entity (or that the authenticated entity has the - necessary permissions to act on behalf of that account identfiier). + necessary permissions to act on behalf of that account identifier). After those checks are done on the remote provider, they call the **ConfirmActivationKey API** to ask the original provider if this activation diff --git a/connection-coordinator/schemas/connection.yaml b/connection-coordinator/schemas/connection.yaml index 8681898..c57544e 100644 --- a/connection-coordinator/schemas/connection.yaml +++ b/connection-coordinator/schemas/connection.yaml @@ -57,7 +57,7 @@ Connection: description: |- When set to true during a CreateConnection request, this indicates that the caller is deferring active provisioning responsibilities to the - receiver. Note, the receiver may refuse to accept the provisioning responsiblity + receiver. Note, the receiver may refuse to accept the provisioning responsibility and reject the request with a 400 error code. type: boolean sourceData: