Fix typos

OnkarRuikar · Mar 27, 2024 · 9b2bb4f · 9b2bb4f
1 parent 5009121
commit 9b2bb4f
Show file tree

Hide file tree

Showing 3 changed files with 3 additions and 3 deletions.
diff --git a/..._testing/client-side_javascript_frameworks/angular_todo_list_beginning/index.md b/..._testing/client-side_javascript_frameworks/angular_todo_list_beginning/index.md
@@ -37,7 +37,7 @@ At this point, we are ready to start creating our to-do list application using A
 
 ## The to-do application structure
 
-Like any web application, an Angular application has an `index.html` as the entry point. The `index.html` acually is the app's top level HTML template:
+Like any web application, an Angular application has an `index.html` as the entry point. The `index.html` actually is the app's top level HTML template:
 
 ```html
 <!doctype html>

diff --git a/files/en-us/mozilla/add-ons/webextensions/manifest.json/content_scripts/index.md b/files/en-us/mozilla/add-ons/webextensions/manifest.json/content_scripts/index.md
@@ -305,7 +305,7 @@ Details of all the keys you can include are given in the table below.
               <p>
                 <strong>Warning:</strong> Due to the lack of isolation, the web page can detect and interfere with the executed code.
                 Do not use the <code>MAIN</code> world unless it is acceptable for web pages to read, access, or modify the logic or data that flows through the executed code.
-                <code>worid</code>, and therefore <code>"MAIN"</code>, is not supported in Firefox (although it is planned, and the work to introduce it is tracked by <a href="https://bugzil.la/1736575" class="external" target="_blank">Bug 1736575</a>). In the meantime, JavaScript code running in the isolated content script sandbox can use the Firefox "Xray vision" feature, as described in <a href="/en-US/docs/Mozilla/Add-ons/WebExtensions/Sharing_objects_with_page_scripts">Share objects with page scripts</a>.
+                <code>world</code>, and therefore <code>"MAIN"</code>, is not supported in Firefox (although it is planned, and the work to introduce it is tracked by <a href="https://bugzil.la/1736575" class="external" target="_blank">Bug 1736575</a>). In the meantime, JavaScript code running in the isolated content script sandbox can use the Firefox "Xray vision" feature, as described in <a href="/en-US/docs/Mozilla/Add-ons/WebExtensions/Sharing_objects_with_page_scripts">Share objects with page scripts</a>.
               </p>
             </div>
           </dd>

diff --git a/files/en-us/web/api/fenced_frame_api/index.md b/files/en-us/web/api/fenced_frame_api/index.md
@@ -89,7 +89,7 @@ Supports-Loading-Mode: fenced-frame
 Other effects of fenced frames on HTTP headers are as follows:
 
 - [User-agent client hints](/en-US/docs/Web/HTTP/Client_hints#user-agent_client_hints) are not available inside fenced frames because they rely on [permissions policy](/en-US/docs/Web/HTTP/Permissions_Policy) delegation, which could be used to leak data.
-- Strict [`Cross-Origin-Opener-Policy`](/en-US/docs/Web/HTTP/Headers/Cross-Origin-Opener-Policy) settings are enforced on new browsing contexts opened from inside frenced frames, otherwise they could be used to leak information to other origins. Any new window opened from inside a fenced frame will have [`rel="noopener"`](/en-US/docs/Web/HTML/Attributes/rel/noopener) and `Cross-Origin-Opener-Policy: same-origin` set to ensure that {{domxref("Window.opener")}} returns `null` and place it in its own browsing context group.
+- Strict [`Cross-Origin-Opener-Policy`](/en-US/docs/Web/HTTP/Headers/Cross-Origin-Opener-Policy) settings are enforced on new browsing contexts opened from inside fenced frames, otherwise they could be used to leak information to other origins. Any new window opened from inside a fenced frame will have [`rel="noopener"`](/en-US/docs/Web/HTML/Attributes/rel/noopener) and `Cross-Origin-Opener-Policy: same-origin` set to ensure that {{domxref("Window.opener")}} returns `null` and place it in its own browsing context group.
 - [`Content-Security-Policy: fenced-frame-src`](/en-US/docs/Web/HTTP/Headers/Content-Security-Policy/fenced-frame-src) has been added for specifying valid sources for nested browsing contexts loaded into `<fencedframe>` elements.
 - [`Content-Security-Policy: sandbox`](/en-US/docs/Web/HTTP/Headers/Content-Security-Policy/sandbox) custom settings cannot be inherited by fenced frames, to mitigate privacy issues. For a fenced frame to load, you need to specify no `sandbox` CSP (which implies the below values), or specify the following sandbox values:
   - `allow-same-origin`