diff --git a/artifacts/CAMARA_common.yaml b/artifacts/CAMARA_common.yaml
index 2bf87fd1..3fe766a4 100644
--- a/artifacts/CAMARA_common.yaml
+++ b/artifacts/CAMARA_common.yaml
@@ -387,7 +387,7 @@ components:
                 status: 403
                 code: INVALID_TOKEN_CONTEXT
                 # message: "{{field}} is not consistent with access token."
-                message: "... is not consistent with access token."
+                message: "Request body is not consistent with access token."
                 # GENERIC_403_{{SPECIFIC_CODE}}:
                 #   description: Indicate a Business Logic condition that forbids a process not attached to a specific field in the context of the API
                 #   value:
diff --git a/documentation/CAMARA-API-Design-Guide.md b/documentation/CAMARA-API-Design-Guide.md
index 83f9ff44..0db4d67e 100644
--- a/documentation/CAMARA-API-Design-Guide.md
+++ b/documentation/CAMARA-API-Design-Guide.md
@@ -431,7 +431,7 @@ In the following, we elaborate on the existing errors. In particular, we identif
 |:----------------:|:-----------------------------:|----------------------------------------------------------------------------|------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|
 |       401        |       `UNAUTHENTICATED`       | Request not authenticated due to missing, invalid, or expired credentials. A new authentication is required. | The request cannot be authenticated and a new authentication is required                                                            |
 |       403        |   `PERMISSION_DENIED`   | Client does not have sufficient permissions to perform this action. | OAuth2 token access does not have the required scope or when the user fails operational security                                |
-|       403        | `INVALID_TOKEN_CONTEXT` | `{{field}}` is not consistent with access token.                    | Reflect some inconsistency between information in some field of the API and the related OAuth2 Token. This error SHOULD be used only when the scope of the API allows it to explicitly confirm whether or not the supplied identity matches that bound to the Three-Legged Access Token.                             |
+|       403        | `INVALID_TOKEN_CONTEXT` | Request body is not consistent with access token.                    | Reflect some inconsistency between information in some field of the API and the related OAuth2 Token. This error SHOULD be used only when the scope of the API allows it to explicitly confirm whether or not the supplied identity matches that bound to the Three-Legged Access Token.                             |
 |       403        |      `{{SPECIFIC_CODE}}`      | `{{SPECIFIC_CODE_MESSAGE}}`                                                | Indicate a Business Logic condition that forbids a process not attached to a specific field in the context of the API (e.g QoD session cannot be created for a set of users) |
 |       404        |          `NOT_FOUND`          | The specified resource is not found.                                       | Resource is not found                                                                                                                               |
 |       404        |     `IDENTIFIER_NOT_FOUND`    | Device identifier not found.                                               | Some identifier cannot be matched to a device                                                                                                                              |