From 8fef4781eb01c018a667143b3b92f68889e20d7e Mon Sep 17 00:00:00 2001 From: Stefan Schultz <28778796+itsmestefanjay@users.noreply.github.com> Date: Tue, 5 Mar 2024 17:55:16 +0100 Subject: [PATCH] Removing possible discriminatory language (#3405) * Replace white-listed with allowed * Replace white-listed with allowed * Fix a typo --- docs/apis-tools/zeebe-api/technical-error-handling.md | 2 +- versioned_docs/version-1.3/apis-tools/grpc.md | 2 +- versioned_docs/version-8.1/apis-tools/grpc.md | 2 +- versioned_docs/version-8.2/apis-tools/grpc.md | 2 +- versioned_docs/version-8.3/apis-tools/grpc.md | 2 +- .../apis-tools/zeebe-api/technical-error-handling.md | 2 +- 6 files changed, 6 insertions(+), 6 deletions(-) diff --git a/docs/apis-tools/zeebe-api/technical-error-handling.md b/docs/apis-tools/zeebe-api/technical-error-handling.md index 1a7ec0e8132..87180286be7 100644 --- a/docs/apis-tools/zeebe-api/technical-error-handling.md +++ b/docs/apis-tools/zeebe-api/technical-error-handling.md @@ -23,7 +23,7 @@ the broker is unavailable, etc.) are reported to the client using the following - If you receive many such errors within a short time period, it indicates the broker is constantly under high load. - It is recommended to reduce the rate of requests. When backpressure is active, the broker may reject any request except _CompleteJob_ RPC and _FailJob_ RPC. - - These requests are white-listed for backpressure and are always accepted by the broker even if it is receiving requests above its limits. + - These requests are allowed during backpressure and are always accepted by the broker even if it is receiving requests above its limits. - `GRPC_STATUS_UNAVAILABLE`: If the gateway itself is in an invalid state (e.g. out of memory). - `GRPC_STATUS_INTERNAL`: For any other internal errors that occurred between the gateway and the broker. diff --git a/versioned_docs/version-1.3/apis-tools/grpc.md b/versioned_docs/version-1.3/apis-tools/grpc.md index ce127ae9461..b53c46dad24 100644 --- a/versioned_docs/version-1.3/apis-tools/grpc.md +++ b/versioned_docs/version-1.3/apis-tools/grpc.md @@ -666,7 +666,7 @@ the broker is unavailable, etc.) are reported to the client using the following - If you receive many such errors within a short time period, it indicates the broker is constantly under high load. - It is recommended to reduce the rate of requests. When back-pressure is active, the broker may reject any request except _CompleteJob_ RPC and _FailJob_ RPC. - - These requests are white-listed for back-pressure and are always accepted by the broker even if it is receiving requests above its limits. + - These requests are allowed during back-pressure and are always accepted by the broker even if it is receiving requests above its limits. - `GRPC_STATUS_UNAVAILABLE`: If the gateway itself is in an invalid state (e.g. out of memory). - `GRPC_STATUS_INTERNAL`: For any other internal errors that occurred between the gateway and the broker. diff --git a/versioned_docs/version-8.1/apis-tools/grpc.md b/versioned_docs/version-8.1/apis-tools/grpc.md index db5fcf86fa8..6d99dc36b64 100644 --- a/versioned_docs/version-8.1/apis-tools/grpc.md +++ b/versioned_docs/version-8.1/apis-tools/grpc.md @@ -807,7 +807,7 @@ the broker is unavailable, etc.) are reported to the client using the following - If you receive many such errors within a short time period, it indicates the broker is constantly under high load. - It is recommended to reduce the rate of requests. When backpressure is active, the broker may reject any request except _CompleteJob_ RPC and _FailJob_ RPC. - - These requests are white-listed for backpressure and are always accepted by the broker even if it is receiving requests above its limits. + - These requests are allowed during backpressure and are always accepted by the broker even if it is receiving requests above its limits. - `GRPC_STATUS_UNAVAILABLE`: If the gateway itself is in an invalid state (e.g. out of memory). - `GRPC_STATUS_INTERNAL`: For any other internal errors that occurred between the gateway and the broker. diff --git a/versioned_docs/version-8.2/apis-tools/grpc.md b/versioned_docs/version-8.2/apis-tools/grpc.md index 8b9e360379c..495a0e9dcc7 100644 --- a/versioned_docs/version-8.2/apis-tools/grpc.md +++ b/versioned_docs/version-8.2/apis-tools/grpc.md @@ -973,7 +973,7 @@ the broker is unavailable, etc.) are reported to the client using the following - If you receive many such errors within a short time period, it indicates the broker is constantly under high load. - It is recommended to reduce the rate of requests. When backpressure is active, the broker may reject any request except _CompleteJob_ RPC and _FailJob_ RPC. - - These requests are white-listed for backpressure and are always accepted by the broker even if it is receiving requests above its limits. + - These requests are allowed during backpressure and are always accepted by the broker even if it is receiving requests above its limits. - `GRPC_STATUS_UNAVAILABLE`: If the gateway itself is in an invalid state (e.g. out of memory). - `GRPC_STATUS_INTERNAL`: For any other internal errors that occurred between the gateway and the broker. diff --git a/versioned_docs/version-8.3/apis-tools/grpc.md b/versioned_docs/version-8.3/apis-tools/grpc.md index 6c9c180f714..423857de1ae 100644 --- a/versioned_docs/version-8.3/apis-tools/grpc.md +++ b/versioned_docs/version-8.3/apis-tools/grpc.md @@ -1123,7 +1123,7 @@ the broker is unavailable, etc.) are reported to the client using the following - If you receive many such errors within a short time period, it indicates the broker is constantly under high load. - It is recommended to reduce the rate of requests. When backpressure is active, the broker may reject any request except _CompleteJob_ RPC and _FailJob_ RPC. - - These requests are white-listed for backpressure and are always accepted by the broker even if it is receiving requests above its limits. + - These requests are allowed during backpressure and are always accepted by the broker even if it is receiving requests above its limits. - `GRPC_STATUS_UNAVAILABLE`: If the gateway itself is in an invalid state (e.g. out of memory). - `GRPC_STATUS_INTERNAL`: For any other internal errors that occurred between the gateway and the broker. diff --git a/versioned_docs/version-8.4/apis-tools/zeebe-api/technical-error-handling.md b/versioned_docs/version-8.4/apis-tools/zeebe-api/technical-error-handling.md index 1a7ec0e8132..87180286be7 100644 --- a/versioned_docs/version-8.4/apis-tools/zeebe-api/technical-error-handling.md +++ b/versioned_docs/version-8.4/apis-tools/zeebe-api/technical-error-handling.md @@ -23,7 +23,7 @@ the broker is unavailable, etc.) are reported to the client using the following - If you receive many such errors within a short time period, it indicates the broker is constantly under high load. - It is recommended to reduce the rate of requests. When backpressure is active, the broker may reject any request except _CompleteJob_ RPC and _FailJob_ RPC. - - These requests are white-listed for backpressure and are always accepted by the broker even if it is receiving requests above its limits. + - These requests are allowed during backpressure and are always accepted by the broker even if it is receiving requests above its limits. - `GRPC_STATUS_UNAVAILABLE`: If the gateway itself is in an invalid state (e.g. out of memory). - `GRPC_STATUS_INTERNAL`: For any other internal errors that occurred between the gateway and the broker.