Resolving PR

lwasylow · lwasylow · commit beb9a3a3207e · 2023-04-26T17:30:32.000-07:00
diff --git a/docs/userguide/annotations.md b/docs/userguide/annotations.md
@@ -1634,7 +1634,7 @@ Tags must follow the below naming convention:
 - tag cannot start with a dash, e.g. `-some-stuff` is **not** a valid tag
 - tag cannot contain spaces, e.g. `test of batch`. To create a multi-word tag use underscores or dashes, e.g. `test_of_batch`, `test-of-batch`
 - leading and trailing spaces are ignored in tag name, e.g. `--%tags(  tag1  ,   tag2  )` becomes `tag1` and `tag2` tag names
-- tag cannot be one of two reserved words : `none` and `any`, any tags with that will not be considered.
+- tag cannot be one of two reserved words: `none` and `any`. `none` and `any` as a tag will be treated as no tag
 
 
 ### Suitepath
diff --git a/docs/userguide/running-unit-tests.md b/docs/userguide/running-unit-tests.md
@@ -325,7 +325,13 @@ Multiple tags are separated by comma.
 
 Tag expressions are boolean expressions created by combining tags with the `!`, `&`, `|` operators. Tag expressions can be grouped using `(` and `)` braces. Grouping tag expressions affects operator precedence.
 
-Two special expressions are supported, `any` and `none`, which select all tests with any tags at all, and all tests without any tags, respectively. These special expressions may be combined with other expressions just like normal tags. When using `none` be aware that if the suite is tagged it will exclude any tests and suites below.
+Two reserved keywords, `any` and `none`, can be used when creating a tag expression to run tests.
+- `any` keyword represents tests and suites with any tags
+- `none` keyword represents tests and suites without tags
+
+These keywords may be combined with other expressions just like normal tags.
+
+**Note:** When specifying `none`, be aware that it will exclude any tests/suites/contexts contained within a tagged suite.
 
 | Operator | Meaning |
 | -------- | --------|
