From c742598d87523e1499ca127ed06351b356ad80a4 Mon Sep 17 00:00:00 2001 From: wbamberg Date: Tue, 17 Dec 2024 19:41:59 -0800 Subject: [PATCH] Update files/en-us/web/api/messagechannel/port2/index.md --- files/en-us/web/api/messagechannel/port2/index.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/files/en-us/web/api/messagechannel/port2/index.md b/files/en-us/web/api/messagechannel/port2/index.md index c18e9449df362c4..85708616689a3be 100644 --- a/files/en-us/web/api/messagechannel/port2/index.md +++ b/files/en-us/web/api/messagechannel/port2/index.md @@ -23,7 +23,7 @@ port attached to the context at the other end of the channel. In the following code block, you can see a new channel being created using the {{domxref("MessageChannel.MessageChannel", "MessageChannel()")}} constructor. When the IFrame has loaded, we pass `port2` to the IFrame using -{{domxref("Window.postMessage")}} along with a message. The +{{domxref("Window.postMessage()")}} along with a message. The `handleMessage` handler then responds to a message being sent back from the IFrame (using {{domxref("MessagePort.message_event", "onmessage")}}), putting it into a paragraph. {{domxref("MessageChannel.port1", "port1")}} is listened to, to check when the message arrives.