typos

Author: lucasfernog-crabnebula

clients/web/src/lib/tauri/config/tauri-conf-schema-v2-zod.ts

@@ -1060,7 +1060,7 @@ export const tauriConfigSchemaV2 = z
                         description: z
                           .string()
                           .describe(
-                            "Description of what the capability is intended to allow on associated windows.\n\n It should contain a description of what the grouped permissions should allow.\n\n ## Example\n\n This capability allows the `main` window access to `filesystem` write related\n commands and `dialog` commands to enable programatic access to files selected by the user.",
+                            "Description of what the capability is intended to allow on associated windows.\n\n It should contain a description of what the grouped permissions should allow.\n\n ## Example\n\n This capability allows the `main` window access to `filesystem` write related\n commands and `dialog` commands to enable programmatic access to files selected by the user.",
                           )
                           .default(""),
                         remote: z
@@ -1315,7 +1315,7 @@ export const tauriConfigSchemaV2 = z
                           .optional(),
                       })
                       .describe(
-                        'A grouping and boundary mechanism developers can use to isolate access to the IPC layer.\n\n It controls application windows fine grained access to the Tauri core, application, or plugin commands.\n If a window is not matching any capability then it has no access to the IPC layer at all.\n\n This can be done to create groups of windows, based on their required system access, which can reduce\n impact of frontend vulnerabilities in less privileged windows.\n Windows can be added to a capability by exact name (e.g. `main-window`) or glob patterns like `*` or `admin-*`.\n A Window can have none, one, or multiple associated capabilities.\n\n ## Example\n\n ```json\n {\n   "identifier": "main-user-files-write",\n   "description": "This capability allows the `main` window on macOS and Windows access to `filesystem` write related commands and `dialog` commands to enable programatic access to files selected by the user.",\n   "windows": [\n     "main"\n   ],\n   "permissions": [\n     "core:default",\n     "dialog:open",\n     {\n       "identifier": "fs:allow-write-text-file",\n       "allow": [{ "path": "$HOME/test.txt" }]\n     },\n   ],\n   "platforms": ["macOS","windows"]\n }\n ```',
+                        'A grouping and boundary mechanism developers can use to isolate access to the IPC layer.\n\n It controls application windows fine grained access to the Tauri core, application, or plugin commands.\n If a window is not matching any capability then it has no access to the IPC layer at all.\n\n This can be done to create groups of windows, based on their required system access, which can reduce\n impact of frontend vulnerabilities in less privileged windows.\n Windows can be added to a capability by exact name (e.g. `main-window`) or glob patterns like `*` or `admin-*`.\n A Window can have none, one, or multiple associated capabilities.\n\n ## Example\n\n ```json\n {\n   "identifier": "main-user-files-write",\n   "description": "This capability allows the `main` window on macOS and Windows access to `filesystem` write related commands and `dialog` commands to enable programmatic access to files selected by the user.",\n   "windows": [\n     "main"\n   ],\n   "permissions": [\n     "core:default",\n     "dialog:open",\n     {\n       "identifier": "fs:allow-write-text-file",\n       "allow": [{ "path": "$HOME/test.txt" }]\n     },\n   ],\n   "platforms": ["macOS","windows"]\n }\n ```',
                       )
                       .describe("An inlined capability."),
                     z