From 71c44980399697d864356616542253a868693a5f Mon Sep 17 00:00:00 2001
From: Dee Dee Rothery <83650384+drothery-edb@users.noreply.github.com>
Date: Mon, 27 Jun 2022 07:37:22 -0400
Subject: [PATCH] consistency changes

---
 .../docs/migration_toolkit/55/08_mtk_command_options.mdx       | 3 +--
 1 file changed, 1 insertion(+), 2 deletions(-)

diff --git a/product_docs/docs/migration_toolkit/55/08_mtk_command_options.mdx b/product_docs/docs/migration_toolkit/55/08_mtk_command_options.mdx
index 4e191cd28e3..f600b3bbbb8 100644
--- a/product_docs/docs/migration_toolkit/55/08_mtk_command_options.mdx
+++ b/product_docs/docs/migration_toolkit/55/08_mtk_command_options.mdx
@@ -608,7 +608,7 @@ ALTER TABLE DEPT ADD CONSTRAINT DEPT_DNAME_UQ UNIQUE (DNAME);
 
 When you then migrate this table and create it in EDB Postgres Advanced Server, all unquoted object names are converted to lowercase letters, so the table appears in EDB Postgres Advanced Server as follows:
 
-```text
+```sql
 Table "edb.dept"
 Column  | Type                  | Modifiers
 --------+-----------------------+-----------
@@ -658,7 +658,6 @@ Applications can then access the object using quoted uppercase names.
 
 ```sql
 useoracase=# SELECT * FROM "DEPT";
-__OUTPUT__
 DEPTNO  | DNAME      | LOC
 --------+------------+----------
 10      | ACCOUNTING | NEW YORK