Update with taroface feedback (1)

Author: rmloveland

src/current/v25.2/create-table-as.md

@@ -78,7 +78,7 @@ The user must have the `CREATE` [privilege]({% link {{ page.version.version }}/s
  `create_as_col_qual_list` | An optional column definition, which may include [primary key constraints]({% link {{ page.version.version }}/primary-key.md %}) and [column family assignments]({% link {{ page.version.version }}/column-families.md %}).
  `family_def` | An optional [column family definition]({% link {{ page.version.version }}/column-families.md %}). Column family names must be unique within the table but can have the same name as columns, constraints, or indexes.
  `create_as_constraint_def` | An optional [primary key constraint]({% link {{ page.version.version }}/primary-key.md %}).
- `select_stmt` | A [selection query]({% link {{ page.version.version }}/selection-queries.md %}) to provide the data.
+ `select_stmt` | A [selection query]({% link {{ page.version.version }}/select-clause.md %}) to provide the data.
  `opt_persistence_temp_table` |  Defines the table as a session-scoped temporary table. For more information, see [Temporary Tables]({% link {{ page.version.version }}/temporary-tables.md %}).<br><br>Note that the `LOCAL`, `GLOBAL`, and `UNLOGGED` options are no-ops, allowed by the parser for PostgreSQL compatibility.<br><br>**Support for temporary tables is [in preview]({% link {{ page.version.version }}/cockroachdb-feature-availability.md %}#temporary-objects)**.
  `opt_with_storage_parameter_list` |  A comma-separated list of [spatial index tuning parameters]({% link {{ page.version.version }}/spatial-indexes.md %}#index-tuning-parameters). Supported parameters include `fillfactor`, `s2_max_level`, `s2_level_mod`, `s2_max_cells`, `geometry_min_x`, `geometry_max_x`, `geometry_min_y`, and `geometry_max_y`. The `fillfactor` parameter is a no-op, allowed for PostgreSQL-compatibility.<br><br>For details, see [Spatial index tuning parameters]({% link {{ page.version.version }}/spatial-indexes.md %}#index-tuning-parameters). For an example, see [Create a spatial index that uses all of the tuning parameters]({% link {{ page.version.version }}/spatial-indexes.md %}#create-a-spatial-index-that-uses-all-of-the-tuning-parameters).
  `ON COMMIT PRESERVE ROWS` | This clause is a no-op, allowed by the parser for PostgreSQL compatibility. CockroachDB only supports session-scoped [temporary tables]({% link {{ page.version.version }}/temporary-tables.md %}), and does not support the clauses `ON COMMIT DELETE ROWS` and `ON COMMIT DROP`, which are used to define transaction-scoped temporary tables in PostgreSQL.
@@ -302,40 +302,35 @@ You can define the [column families]({% link {{ page.version.version }}/column-f
 The timestamp must be within the [garbage collection (GC) window]({% link {{ page.version.version }}/architecture/storage-layer.md %}#garbage-collection) of the source table for the data to be available.
 {{site.data.alerts.end}}
 
-The syntax for creating a new table from a historical table at a given timestamp is as follows; this example creates a new table at the most recent timestamp that can perform a [follower read]({% link {{ page.version.version }}/follower-reads.md %}).
+The following example creates a new table from the [`movr`]({% link {{ page.version.version }}/movr.md %}) dataset at the most recent timestamp that can perform a [follower read]({% link {{ page.version.version }}/follower-reads.md %}).
 
 {% include_cached copy-clipboard.html %}
 ~~~ sql
 CREATE TABLE analysis_vehicle_location_histories
-  AS SELECT * FROM vehicle_location_histories
+  AS SELECT * FROM movr.vehicle_location_histories
   AS OF SYSTEM TIME follower_read_timestamp();
 ~~~
 
+~~~
+CREATE TABLE AS
+~~~
+
 #### Undo an accidental table deletion
 
-The following steps show how to undo an accidental table deletion using `CREATE TABLE AS ... AS OF SYSTEM TIME`.
+The following steps use a table from the [`movr`]({% link {{ page.version.version }}/movr.md %}) dataset to show how to undo an accidental table deletion using `CREATE TABLE AS ... AS OF SYSTEM TIME`.
 
-1. Create and populate a table:
-
-    {% include_cached copy-clipboard.html %}
-    ~~~ sql
-    CREATE TABLE customers (
-        id INT PRIMARY KEY,
-        name STRING
-    );
-
-    INSERT INTO customers (id, name) VALUES (1, 'Alice'), (2, 'Bob');
-    ~~~
-
-1. Get a timestamp from before the table is deleted:
+1. Get a timestamp before the table is deleted in an upcoming step:
 
     {% include_cached copy-clipboard.html %}
     ~~~ sql
     SELECT now();
     ~~~
 
     ~~~
-    2025-06-09 19:55:40.286833+00
+                  now
+    --------------------------------
+      2025-06-17 15:04:15.82632+00
+    (1 row)
     ~~~
 
 1. Wait a few seconds to simulate time passing (adjust as needed):
@@ -345,18 +340,29 @@ The following steps show how to undo an accidental table deletion using `CREATE
     SELECT pg_sleep(5);
     ~~~
 
+    ~~~
+      pg_sleep
+    ------------
+         t
+    (1 row)
+    ~~~
+
 1. Drop the original table:
 
     {% include_cached copy-clipboard.html %}
     ~~~ sql
-    DROP TABLE customers;
+    DROP TABLE movr.vehicle_location_histories;
+    ~~~
+
+    ~~~
+    DROP TABLE
     ~~~
 
-1. Restore the table using the [`AS OF SYSTEM TIME`]({% link {{ page.version.version }}/as-of-system-time.md %}) clause:
+1. Restore the table using the [`AS OF SYSTEM TIME`]({% link {{ page.version.version }}/as-of-system-time.md %}) clause and the timestamp you obtained before dropping the table:
 
     {% include_cached copy-clipboard.html %}
     ~~~ sql
-    CREATE TABLE customers_restored AS SELECT * FROM customers AS OF SYSTEM TIME '2025-06-09 19:55:40.286833+00';
+    CREATE TABLE movr.vehicle_location_histories AS SELECT * FROM movr.vehicle_location_histories AS OF SYSTEM TIME '2025-06-17 15:04:15.82632+00';
     ~~~
 
     ~~~