Fix dead links

Author: cezaraugusto

docs/en/docs/development/content-scripts.mdx

@@ -13,7 +13,7 @@ Extension.js manages content scripts by performing the following actions:
 
 1. **Process Script Files:** All JavaScript and CSS files declared in the `content_scripts` field of the `manifest.json` are compiled, bundled, and emitted.
 2. **Inject CSS for Hot-Module Replacement (HMR):** During development, Extension.js injects CSS files dynamically to support HMR, ensuring seamless updates without a full page reload.
-3. **Maintain Isolation:** Content scripts operate in an isolated environment, ensuring no direct access to the page’s JavaScript context.
+3. **Maintain Isolation:** Content scripts operate in an isolated environment, ensuring no direct access to the page's JavaScript context.
 
 ## Content Scripts Support
 
@@ -78,4 +78,4 @@ dist/
 ## Next Steps
 
 - For further details on using special folders, refer to the [Special Folders documentation](../features/special-folders.mdx).
-- Learn about managing resources with [Web-Accessible Resources](./web_accessible_resources).
+- Learn about managing resources with [Web-Accessible Resources](./web-accessible-resources).

docs/en/docs/development/icons.mdx

@@ -31,7 +31,7 @@ The following manifest fields are used to declare icons:
 
 ## Where Icons Appear in Extensions
 
-Icons can appear in different locations across the browser interface, based on where they’re declared in `manifest.json`:
+Icons can appear in different locations across the browser interface, based on where they're declared in `manifest.json`:
 
 - **Toolbar Icons:** The `action.default_icon` or `browser_action.default_icon` fields add an icon in the browser's toolbar, making it visible next to the address bar for user interaction.
 - **Context Menus:** Declaring icons in `page_action.default_icon` provides a unique icon specific to certain pages, visible only when defined pages are active.
@@ -193,11 +193,11 @@ dist/
 
 ## Best Practices
 
-- **Organize with `/public/` Folder:** Place additional icons not declared in the manifest within the `/public` folder to keep project structure clear and ensure they’re accessible if needed.
-- **Declare Icons in `manifest.json`:** Always declare icons in the manifest file to ensure they’re correctly bundled in the build process.
+- **Organize with `/public/` Folder:** Place additional icons not declared in the manifest within the `/public` folder to keep project structure clear and ensure they're accessible if needed.
+- **Declare Icons in `manifest.json`:** Always declare icons in the manifest file to ensure they're correctly bundled in the build process.
 - **Provide Multiple Resolutions:** Offer icons in multiple resolutions (e.g., `16px`, `48px`, `128px`) to support various device pixel ratios, ensuring icons display clearly on all devices.
 
 ## Next Steps
 
 - For handling icons and other assets, learn more about [Special Folders](../features/special-folders.mdx).
-- Review Extension.js’s [Documentation on Web-Accessible Resources](../development/web_accessible_resources) for additional guidance on managing accessible assets.
+- Review Extension.js's [Documentation on Web-Accessible Resources](../development/web-accessible-resources) for additional guidance on managing accessible assets.