From 34994ce02eca76b64b2a23b8759227b67d81cb30 Mon Sep 17 00:00:00 2001 From: Sebastian Malton Date: Fri, 21 May 2021 15:14:11 -0400 Subject: [PATCH] more doc fixes Signed-off-by: Sebastian Malton --- docs/extensions/guides/ipc.md | 6 +++--- 1 file changed, 3 insertions(+), 3 deletions(-) diff --git a/docs/extensions/guides/ipc.md b/docs/extensions/guides/ipc.md index 4e1f31ffdd..b6ec38eacd 100644 --- a/docs/extensions/guides/ipc.md +++ b/docs/extensions/guides/ipc.md @@ -27,10 +27,10 @@ Both `main` and `renderer` can do this sort of IPC. This is more like a Remote Procedure Call (RPC) or Send-Receive-Reply (SRR). With this sort of communication the caller needs to wait for the result from the other side. -This is accomplished by `await`-int the returned `Promise`. +This is accomplished by `await`-ing the returned `Promise`. This is a unidirectional form of communication. -Only `renderer` can initiate this kind of request, and only `main` can and respond this this kind of request. +Only `renderer` can initiate this kind of request, and only `main` can and respond to this kind of request. ## Registering IPC Handlers and Listeners @@ -76,7 +76,7 @@ function onInitialize(event: Types.IpcMainEvent, id: string) { ``` In other files, it is not necessary to pass around any instances. -It should be able to just call `IpcMain.getInstance()` anywhere it is needed in your extension. +You should be able to just call `IpcMain.getInstance()` anywhere it is needed in your extension. ---