diff --git a/apps/docs/content/troubleshooting/error-index-row-size-exceeds-btree-version-4-maximum-for-index-LMmoeU.mdx b/apps/docs/content/troubleshooting/error-index-row-size-exceeds-btree-version-4-maximum-for-index-LMmoeU.mdx
index f2cc1658061..de377b2e166 100644
--- a/apps/docs/content/troubleshooting/error-index-row-size-exceeds-btree-version-4-maximum-for-index-LMmoeU.mdx
+++ b/apps/docs/content/troubleshooting/error-index-row-size-exceeds-btree-version-4-maximum-for-index-LMmoeU.mdx
@@ -39,13 +39,13 @@ One of the measures of index efficiency is the ratio of index entries to the wid
 The solution is simple: use some king of hashing to transfer the values to much narrower space. I.e. md5. The solution is simple, you build a functional index (=index by expression):
 
 ```sql
-CREATE INDEX ON table_name(MD5(column_name));
+create index on table_name (MD5(column_name));
 ```
 
 instead of:
 
 ```sql
-CREATE INDEX ON table_name(column_name);
+create index on table_name (column_name);
 ```
 
 Then you must modify you SELECTs to be using the same function (otherwise the functional index will not be used in SELECT queries). I.e.
diff --git a/packages/ui-patterns/package.json b/packages/ui-patterns/package.json
index 91984b2f198..39e7e8f6034 100644
--- a/packages/ui-patterns/package.json
+++ b/packages/ui-patterns/package.json
@@ -671,4 +671,4 @@
   "peerDependencies": {
     "next": "catalog:"
   }
-}
\ No newline at end of file
+}