diff --git a/rm-community/rm-community-rest-api-explorer/src/main/webapp/definitions/ig-core-api.yaml b/rm-community/rm-community-rest-api-explorer/src/main/webapp/definitions/ig-core-api.yaml
index 120b40c21b..ade891e07b 100644
--- a/rm-community/rm-community-rest-api-explorer/src/main/webapp/definitions/ig-core-api.yaml
+++ b/rm-community/rm-community-rest-api-explorer/src/main/webapp/definitions/ig-core-api.yaml
@@ -200,9 +200,10 @@ paths:
         Create a fileplan component as a primary child of node **fileplanComponentId**.
 
         This API method supports file upload using multipart/form-data.
+        Electronic records are the only nodes that have content.
 
         Use the **filedata** field to represent the content to upload.
-        You can use a **name** field to give an alternative name for the new file.
+        You can use a **name** field to give an alternative name for the new electronic record.
 
         For multipart/form-data upload you can use the **renditions** field to create renditions (e.g. doclib) asynchronously upon upload.
         Note that currently only one rendition can be requested. Also, as requesting rendition is a background process,
@@ -286,6 +287,14 @@ paths:
         }
         ```
 
+        You can create an empty electronic record and use the record endpoint to create content:
+        ```JSON
+        {
+          "name":"My Electronic Record",
+          "nodeType":"cm:content"
+        }
+        ```
+
         You can create a fileplan component inside a container hierarchy:
         ```JSON
         {