Describe the bug
See screenshot. Should be don't not don't

To Reproduce
Steps to reproduce the behavior:

1. Install latest 4.0 windows client
2. Add cluster
3. Go to cluster settings
4. Read text for "accessible Napespaces"

Expected behavior
Escaped cor

Context: https://twitter.com/bwplotka/status/1334404169432788992

Help wanted 🤗

During meetings right now, it's kinda hectic with dead chat as people will interrupt and talk over each other since alive players can't hear dead players. Add some key to toggle to a "dead only chat" where dead players can discuss stuff without having to talk over the alive players trying to vote people out.

Make players in ghost chat only audible to other players in ghost chat to reduce confus

Please make sure that this is a documentation issue. As per our GitHub Policy, we only address code/doc bugs, performance issues, feature requests and build/installation issues on GitHub. tag:doc_template

System information

• TensorFlow version: 1.13.1
• Doc Link: https://www.tensorflow.org/api_docs/python/tf/cus

They should take single matcher during construction, and their match method should take a generic range, using the new generic matcher support.

Expected usage:

REQUIRE_THAT(get_keys(), AllMatch(KeyPattern({1, 2, 3})));
REQUIRE_THAT(get_numbers(), NoneMatch(IsOdd{}));
REQUIRE_THAT(get_strings(), AnyMatch(Contains("webscale") && !Contains("MongoDB")));

the matching semantics

I think we should patch test/CMakeLists.txt to always use -Wall -Werror on *nix and the corresponding MSVC flags. It is way too easy to overlook a warning in the CI output as #1797 has shown.

@nlohmann Thoughts?

In the documentation user-guide for linting, the example script's docker command is broken.

It seems like the docker command broke since the image was changed.

The following command does work, and I would be happy to modify the script to imp