From 6a07018016bc564d826653d97e9b1381095768e7 Mon Sep 17 00:00:00 2001
From: WofWca <wofwca@protonmail.com>
Date: Mon, 17 Mar 2025 22:27:57 +0400
Subject: [PATCH 1/3] mention that events use commands internally

This is important to mention to make it clear to the developer
what they need to do to secure their application.
---
 .../docs/concept/Inter-Process Communication/index.mdx      | 6 ++++++
 1 file changed, 6 insertions(+)

diff --git a/src/content/docs/concept/Inter-Process Communication/index.mdx b/src/content/docs/concept/Inter-Process Communication/index.mdx
index 3117111cdf..79431fa78b 100644
--- a/src/content/docs/concept/Inter-Process Communication/index.mdx	
+++ b/src/content/docs/concept/Inter-Process Communication/index.mdx	
@@ -54,6 +54,12 @@ Core -> Frontend: "Event"{style.animated: true}
 <figcaption>Events sent between the Core and the Webview.</figcaption>
 </figure>
 
+{/* This is important to mention to make it clear to the developer
+what they need to do to secure their application. */}
+Under the hood, events still utilize Commands,
+and the access to the events API is controlled by the
+[Event permissions](/reference/acl/core-permissions/#event).
+
 ## Commands
 
 Tauri also provides a [foreign function interface]-like abstraction on top of IPC messages[^1]. The primary API, `invoke`, is similar to the browser's `fetch` API and allows the Frontend to invoke Rust functions, pass arguments, and receive data.

From 0fc9bda7e61a621e23bf6dee987b915d1c3a16a1 Mon Sep 17 00:00:00 2001
From: Ayres Vitor <gitkey@virtuaires.com.br>
Date: Fri, 2 May 2025 20:18:42 -0300
Subject: [PATCH 2/3] fix comment

---
 .../docs/concept/Inter-Process Communication/index.mdx        | 4 ++--
 1 file changed, 2 insertions(+), 2 deletions(-)

diff --git a/src/content/docs/concept/Inter-Process Communication/index.mdx b/src/content/docs/concept/Inter-Process Communication/index.mdx
index 79431fa78b..1feeec687c 100644
--- a/src/content/docs/concept/Inter-Process Communication/index.mdx	
+++ b/src/content/docs/concept/Inter-Process Communication/index.mdx	
@@ -54,8 +54,8 @@ Core -> Frontend: "Event"{style.animated: true}
 <figcaption>Events sent between the Core and the Webview.</figcaption>
 </figure>
 
-{/* This is important to mention to make it clear to the developer
-what they need to do to secure their application. */}
+{/* This is important to mention to make it clear to the developer what they need to do to secure their application. */}
+
 Under the hood, events still utilize Commands,
 and the access to the events API is controlled by the
 [Event permissions](/reference/acl/core-permissions/#event).

From a356c4e8e0a8f8ab1d0e5d13fc42223e73731bf9 Mon Sep 17 00:00:00 2001
From: Ayres Vitor <gitkey@virtuaires.com.br>
Date: Fri, 2 May 2025 20:24:30 -0300
Subject: [PATCH 3/3] fix multiline text

---
 .../docs/concept/Inter-Process Communication/index.mdx        | 4 +---
 1 file changed, 1 insertion(+), 3 deletions(-)

diff --git a/src/content/docs/concept/Inter-Process Communication/index.mdx b/src/content/docs/concept/Inter-Process Communication/index.mdx
index 1feeec687c..19176716a9 100644
--- a/src/content/docs/concept/Inter-Process Communication/index.mdx	
+++ b/src/content/docs/concept/Inter-Process Communication/index.mdx	
@@ -56,9 +56,7 @@ Core -> Frontend: "Event"{style.animated: true}
 
 {/* This is important to mention to make it clear to the developer what they need to do to secure their application. */}
 
-Under the hood, events still utilize Commands,
-and the access to the events API is controlled by the
-[Event permissions](/reference/acl/core-permissions/#event).
+Under the hood, events still utilize Commands, and the access to the events API is controlled by the [Event permissions](/reference/acl/core-permissions/#event).
 
 ## Commands