diff --git a/docs/api/ipc-renderer.md b/docs/api/ipc-renderer.md
index 96936632563e..d8f344a204a9 100644
--- a/docs/api/ipc-renderer.md
+++ b/docs/api/ipc-renderer.md
@@ -52,7 +52,7 @@ The `ipcRenderer` module has the following methods for sending messages:
 * `arg` (optional)
 
 Send an event to the main process asynchronously via a `channel`, you can also
-send arbitrary arguments. The main process handles it by listening for the
+send arbitrary arguments. Arguments will be serialized (json) and hence no functions or prototype chain will be included. The main process handles it by listening for the
 `channel` event with `ipcMain`.
 
 ### `ipcRenderer.sendSync(channel[, arg1][, arg2][, ...])`
diff --git a/docs/api/web-contents.md b/docs/api/web-contents.md
index afdd08c4d005..61c2ab1f6919 100644
--- a/docs/api/web-contents.md
+++ b/docs/api/web-contents.md
@@ -693,7 +693,7 @@ Opens the developer tools for the service worker context.
 * `arg` (optional)
 
 Send an asynchronous message to renderer process via `channel`, you can also
-send arbitrary arguments. The renderer process can handle the message by
+send arbitrary arguments. Arguments will be serialized (json) and hence no functions or prototype chain will be included. The renderer process can handle the message by
 listening to the `channel` event with the `ipcRenderer` module.
 
 An example of sending messages from the main process to the renderer process: