From c571626ba93b79cab64fa7b22c825d99085630ca Mon Sep 17 00:00:00 2001 From: Suraj Deshmukh Date: Sun, 8 Oct 2017 20:48:44 +0530 Subject: [PATCH] (labels docs): correct description of logical AND (#5804) --- docs/concepts/overview/working-with-objects/labels.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/docs/concepts/overview/working-with-objects/labels.md b/docs/concepts/overview/working-with-objects/labels.md index 8e577c87e4..b804f26d0f 100644 --- a/docs/concepts/overview/working-with-objects/labels.md +++ b/docs/concepts/overview/working-with-objects/labels.md @@ -51,7 +51,7 @@ Unlike [names and UIDs](/docs/user-guide/identifiers), labels do not provide uni Via a _label selector_, the client/user can identify a set of objects. The label selector is the core grouping primitive in Kubernetes. The API currently supports two types of selectors: _equality-based_ and _set-based_. -A label selector can be made of multiple _requirements_ which are comma-separated. In the case of multiple requirements, all must be satisfied so the comma separator acts as an _AND_ logical operator. +A label selector can be made of multiple _requirements_ which are comma-separated. In the case of multiple requirements, all must be satisfied so the comma separator acts as a logical _AND_ (`&&`) operator. An empty label selector (that is, one with zero requirements) selects every object in the collection.