AWS prescriptive-guidance documentation change

Service: prescriptive-guidance · 2026-07-10 · Documentation low

File: prescriptive-guidance/latest/postgresql-query-tuning/explain-query-plan.md

Summary

Updated formatting of warning note, changed image path, and modified navigation link text. No technical content changes beyond presentation improvements

Security assessment

Changes are purely editorial/formatting. The existing warning about EXPLAIN ANALYZE with DML statements remains unchanged in substance. No security-related content added or modified.

Diff

diff --git a/prescriptive-guidance/latest/postgresql-query-tuning/explain-query-plan.md b/prescriptive-guidance/latest/postgresql-query-tuning/explain-query-plan.md
index 41a7e978a..936596607 100644
--- a//prescriptive-guidance/latest/postgresql-query-tuning/explain-query-plan.md
+++ b//prescriptive-guidance/latest/postgresql-query-tuning/explain-query-plan.md
@@ -30,3 +30,2 @@ In PostgreSQL, `EXPLAIN` will only generate a plan for the given statement. If y
-###### Important
-
-When using `EXPLAIN ANALYZE`, be careful with `INSERT`, `UPDATE`, and `DELETE`.
+Important: When using `EXPLAIN ANALYZE`, be careful with `INSERT`, `UPDATE`, and `DELETE`.  
+---  
@@ -55 +54 @@ The following screenshot shows the query plan for a sequential scan.
-![Query plan shown on the Data Output tab in pgAdmin.](/images/prescriptive-guidance/latest/postgresql-query-tuning/images/query-plan.png)
+![Query plan shown on the Data Output tab in pgAdmin.](/images/prescriptive-guidance/latest/postgresql-query-tuning/images/guide-img/7b8a9711-9513-471f-b676-8df14916e186/images/30249088-2899-462f-8b65-fd26730cccdb.png)
@@ -80 +79 @@ Introduction
-Next
+Use cases for tuning queries