[DO NOT CLOSE] Typo error found during the translation

[majinghe]

This issue is used to record the typo error found during the translation, once the translation is done, will open an issue to upstream community to confirm.

• File docs/root/configuration/upstream/cluster_manager/cluster_runtime.rst

• File docs/root/install/building.rst

• File docs/root/configuration/security/secret.rst

Upstream clusters are handled in a similar way, if a cluster client certificate needs to be fetched by SDS remotely, it will NOT be marked as active and it will not be used before the certificates are fetched. If Envoy fails to fetch the certificates due to connection failures, or bad response data, the cluster will be marked as active, it can be used to handle the requests, but the requests routed to that cluster will be rejected.

If Envoy fails to fetch the certificates due to connection failures, or bad response data, the cluster will be marked as active
should be
If Envoy fails to fetch the certificates due to connection failures, or bad response data, the cluster will be marked as NOT active?

[WisWang]

File docs/root/configuration/http/http_filters/jwt_authn_filter.rst 58行：

The *provider_name* must be unique, it is referred in the `JwtRequirement <envoy_v3_api_msg_extensions.filters.http.jwt_authn.v3.JwtRequirement>` in its *provider_name* field.
should be
The *provider_name* must be unique, it is referred in the :ref:`JwtRequirement <envoy_v3_api_msg_extensions.filters.http.jwt_authn.v3.JwtRequirement>` in its *provider_name* field.

miss a :ref:

[Edward-Gavin]

File docs/root/configuration/http/http_conn_man/response_code_details.rst line 41 and line 42 is duplicated,

41: response_payload_too_large, Envoy is doing non-streaming proxying and the response payload exceeded configured limits.
42: response_payload_too_large, Envoy is doing non-streaming proxying and the response payload exceeded configured limits.

please delete one line.