Address Kirk's comments

Author: quinntaylormitchell

docs/src/user-guide/quick-start/clp-json.md

@@ -61,7 +61,7 @@ To compress logs from object storage, see
 
 ### Sample logs
 
-For some sample logs, check out the open-source [datasets](../resources-datasets).
+For some sample logs, check out the [open-source datasets](../resources-datasets).
 
 ---
 
@@ -70,12 +70,24 @@ For some sample logs, check out the open-source [datasets](../resources-datasets
 You can search your compressed logs from CLP's [UI](#searching-from-the-ui) or the
 [command line](#searching-from-the-command-line).
 
-Queries must be in the form of a set of conditions (predicates) on key-value pairs (kv-pairs). For
-example, consider the logs in [Figure 1](#figure-1) and the query in [Figure 2](#figure-2).
+In clp-json, queries are written as a set of conditions (predicates) on key-value pairs (kv-pairs).
+For example, [Figure 1](#figure-1) shows a query that matches the first log event in
+[Figure 2](#figure-2).
 
 (figure-1)=
 :::{card}
 
+```sql
+ctx: "conn11" AND msg: "*write concern*"
+```
+
++++
+**Figure 1**: An example query.
+:::
+
+(figure-2)=
+:::{card}
+
 ```json lines
 {
   "t": {
@@ -93,23 +105,12 @@ example, consider the logs in [Figure 1](#figure-1) and the query in [Figure 2](
 ```
 
 +++
-**Figure 1**: A set of JSON log events.
-:::
-
-(figure-2)=
-:::{card}
-
-```sql
-ctx: "conn11" AND msg: "*write concern*"
-```
-
-+++
-**Figure 2**: An example query.
+**Figure 2**: A set of JSON log events.
 :::
 
 The query in [Figure 2](#figure-2) will match log events that contain the kv-pair `"ctx": "conn11"`
 as well as a kv-pair with key `"msg"` and a value that matches the wildcard query
-`"*write concern*"`. This query will match the first log event in [Figure 1](#figure-1).
+`"*write concern*"`.
 
 A complete reference for clp-json's query syntax is available on the
 [JSON syntax reference page](../reference-json-search-syntax).
@@ -131,8 +132,8 @@ the following features:
    * You can click and drag to zoom into a time range, or use the time range filter in (4).
 3. The table displays the search results for your query.
 4. Clicking the <i class="fa fa-bars"></i> icon reveals additional filters for your query.
-   * The time range filter allows you to specify the period of time that matching log events must
-     be in.
+   * The time range filter allows you to specify the period of time that matching log events must be
+     in.
    * The case sensitivity filter allows you to specify whether CLP should respect the case of your
      query.
 5. Clicking the <i class="fa fa-cog"></i> icon reveals options for displaying results.

docs/src/user-guide/quick-start/clp-text.md

@@ -5,7 +5,7 @@ text logs.
 
 :::{caution}
 If you're using a `clp-text` release, you should only compress unstructured text logs. `clp-text`
-is able to compress and search JSON logs as if it was unstructured text, but `clp-text` cannot
+is able to compress and search JSON logs as if they were unstructured text, but `clp-text` cannot
 query individual fields. This limitation will be addressed in a future version of CLP.
 :::
 
@@ -54,63 +54,68 @@ For some sample logs, check out the [open-source datasets](../resources-datasets
 You can search your compressed logs from CLP's [UI](#searching-from-the-ui) or the
 [command line](#searching-from-the-command-line).
 
-Unstructured text log queries are written as plain text. You can use a couple of special
-characters to make these queries more versatile. `*` can be used as a placeholder for an unknown
-number of characters, and `?` can be used for a single character. For example, consider the logs in
-[Figure 1](#figure-1) and the query in [Figure 2](#figure-2).
+In clp-text, queries are written as wildcard expressions. A wildcard expression is a plain text
+query where:
+
+* `*` matches zero or more characters
+* `?` matches any single character
+
+For example, consider the query in [Figure 1](#figure-1) and the logs in [Figure 2](#figure-2).
 
 (figure-1)=
 :::{card}
 
-```text
-1   abc
-2   axbc
-3   abxc
-4   axxbxc
-5   a b c
+```bash
+"INFO container_? Transitioned*ACQUIRED"
 ```
 
 +++
-**Figure 1**: A set of unstructured text log events.
+**Figure 1**: An example query.
 :::
 
 (figure-2)=
 :::{card}
 
-```bash
-"a*b?c"
+```text
+2015-03-23T15:50:17.926Z INFO container_1 Transitioned from ALLOCATED to ACQUIRED
+2015-03-23T15:50:17.927Z ERROR Scheduler: Error trying to assign container token
+java.lang.IllegalArgumentException: java.net.UnknownHostException: i-e5d112ea
+    at org.apache.hadoop.security.buildTokenService(SecurityUtil.java:374)
+    at org.apache.hadoop.ipc.Server$Handler.run(Server.java:2033)
+Caused by: java.net.UnknownHostException: i-e5d112ea
+    ... 17 more
 ```
 
 +++
-**Figure 2**: An example query.
+**Figure 2**: A set of unstructured text log events.
 :::
 
-The query in [Figure 2](#figure-2) will match with lines 3, 4, and 5 in [Figure 1](#figure-1), as
-they are the only lines which contain the character `"a"` followed by any number (including zero)
-of other characters, followed by `"b"`, followed by one other character, followed by `"c"`.
+The query in [Figure 2](#figure-2) will match with the first log message, as the `?` will stand in
+for any one character (in this case, `1`), and the `*` will stand in for the characters
+` from ALLOCATED to `.
 
 A complete reference for clp-text's query syntax is available on the
 [text syntax reference page](../reference-text-search-syntax).
 
 ### Searching from the UI
 
-To search your compressed logs from CLP's UI, open [http://localhost:4000](http://localhost:4000)
-in your browser (if you changed `webui.host` or `webui.port` in `etc/clp-config.yml`, use the new
+To search your compressed logs from CLP's UI, open [http://localhost:4000](http://localhost:4000) in
+your browser (if you changed `webui.host` or `webui.port` in `etc/clp-config.yml`, use the new
 values).
 
 :::{image} clp-search-ui.png
 :::
 
-The image above shows the search page after running a query. The numbered circles correspond to
-the following features:
+The image above shows the search page after running a query. The numbered circles correspond to the
+following features:
 
 1. The search box is where you can enter your query.
 2. The timeline shows the number of results across the time range of your query.
    * You can click and drag to zoom into a time range, or use the time range filter in (4).
 3. The table displays the search results for your query.
 4. Clicking the <i class="fa fa-bars"></i> icon reveals additional filters for your query.
-   * The time range filter allows you to specify the period of time that matching log events must
-     be in.
+   * The time range filter allows you to specify the period of time that matching log events must be
+     in.
    * The case sensitivity filter allows you to specify whether CLP should respect the case of your
      query.
 5. Clicking the <i class="fa fa-cog"></i> icon reveals options for displaying results.