diff --git a/content/en/docs/Developerguide/creating-dropping-an-mot-table.md b/content/en/docs/Developerguide/creating-dropping-an-mot-table.md
index 3aa869a0f1bfef2e8314e63a55202f0a3572dc34..5b468b8bf77cbe0f7d1f5d1f17e804ca97011ae4 100644
--- a/content/en/docs/Developerguide/creating-dropping-an-mot-table.md
+++ b/content/en/docs/Developerguide/creating-dropping-an-mot-table.md
@@ -11,6 +11,7 @@ Creating a Memory Optimized Table \(MOT\) is very simple. Only the create and dr
- Always use the FOREIGN keyword to refer to MOT tables.
- The \[server mot\_server\] part is optional when creating an MOT table because MOT is an integrated engine, not a separate server.
- The above is an extremely simple example creating a table named **test** with a single integer column named **x**. In the next section \(**Creating an Index**\) a more realistic example is provided.
+- MOT tables cannot be created if incremental checkpoint is enabled in postgresql.conf.
- To drop an MOT table named test –
```
diff --git a/content/en/docs/Developerguide/mot-sql-coverage-and-limitations.md b/content/en/docs/Developerguide/mot-sql-coverage-and-limitations.md
index 28a848ae0af430d772a0132ac6bc3dfe230d1f71..6c2ef2d080974bcb546e53be9953c039f0517f02 100644
--- a/content/en/docs/Developerguide/mot-sql-coverage-and-limitations.md
+++ b/content/en/docs/Developerguide/mot-sql-coverage-and-limitations.md
@@ -37,6 +37,9 @@ The following lists the functionality limitations of MOT tables –
- Partition by range
- Create table with no-logging clause
- DEFERRABLE primary key
+- Reindex
+- Tablespace
+- Create schema with subcommands
## Unsupported Data Types
@@ -168,6 +171,8 @@ The following lists the functionality limitations of MOT tables –
- Select into
- Update on conflict
- Update from
+- Lock table
+- Copy from table
## Unsupported Queries for Native Compilation and Lite Execution