diff --git a/use-timescale/data-tiering/about-data-tiering.md b/use-timescale/data-tiering/about-data-tiering.md
index a5bbcf04c0..3b8f2e2bb9 100644
--- a/use-timescale/data-tiering/about-data-tiering.md
+++ b/use-timescale/data-tiering/about-data-tiering.md
@@ -11,9 +11,7 @@ cloud_ui:
 
 # About data tiering
 
-Save on storage costs by tiering rarely used data to a low-cost object storage layer.
-
-Timescale includes traditional disk storage, and a low-cost object storage
+Timescale Cloud services include traditional disk storage, and a low-cost object storage
 layer built on Amazon S3. You can move your hypertable data across the different
 storage tiers to get the best price performance. You can use primary storage for
 data that requires quick access, and low-cost object storage for rarely used historical
diff --git a/use-timescale/data-tiering/manual-tier-chunk.md b/use-timescale/data-tiering/manual-tier-chunk.md
index cb73b713b5..fd395b2478 100644
--- a/use-timescale/data-tiering/manual-tier-chunk.md
+++ b/use-timescale/data-tiering/manual-tier-chunk.md
@@ -9,8 +9,9 @@ tags: [ storage, data management ]
 # Manually tiering chunks
 
 Once Data Tiering has been enabled on a service individual chunks from a Hypertable may be tiered to object storage.
-
 Before you start, you need a list of chunks to tier. In this example, you use a hypertable called example, and tier chunks older than three days.
+Tiered storage data cannot be modified - so inserts, updates, and deletes will not work on tiered data. So make sure that
+you are not tiering data that is being <\b>actively modified<\b> to tiered storage
 
 <Procedure>
 
@@ -26,8 +27,6 @@ Before you start, you need a list of chunks to tier. In this example, you use a
 1. This returns a list of chunks. Take a note of the chunk names:
 
    ```sql
-   ||show_chunks|
-   |---|---|
    |1|_timescaledb_internal_hyper_1_2_chunk|
    |2|_timescaledb_internal_hyper_1_3_chunk|
    ```
@@ -68,6 +67,16 @@ informational view:
 SELECT * FROM timescaledb_osm.tiered_chunks;
 ```
 
+## Find chunks that are scheduled to be tiered
+
+Chunks are tiered asynchronously. Chunks are tiered one at a time in order to minimize db resource
+consumption during the tiering process. You can see chunks scheduled for tiering (either by the policy or
+ by a manual call to `tier_chunk`) but have not yet been moved to tiered storage using this view.
+
+```sql
+SELECT * FROM timescaledb_osm.chunks_queued_for_tiering ;
+```
+
 If you need to untier your data, see the
 [manually untier data][untier-data] section.
 
diff --git a/use-timescale/data-tiering/tour-data-tiering.md b/use-timescale/data-tiering/tour-data-tiering.md
index 9651e940fb..df0c0ba74e 100644
--- a/use-timescale/data-tiering/tour-data-tiering.md
+++ b/use-timescale/data-tiering/tour-data-tiering.md
@@ -68,7 +68,7 @@ You can view chunks in the tiering queue, that is, chunks that are scheduled
  to be tiered, by using this query.
 
 ```
-try=# SELECT * FROM timescaledb_osm.chunks_queued_for_tiering ;
+SELECT * FROM timescaledb_osm.chunks_queued_for_tiering ;
 -[ RECORD 1 ]-----+-----------------
 hypertable_schema | public
 hypertable_name   | metrics_table