Fix typos: duplicate words and spelling errors across docs and release notes (#9623)

- Remove duplicate 'the' in v1_73.md and v1_96.md release notes
- Fix 'in in' -> 'is in' in v1_89.md release notes
- Remove duplicate 'that' in v1_91.md release notes
- Remove duplicate 'that' and fix 'do be' -> 'to be' in remote-release-notes/v1_53.md
- Fix 'within in' -> 'within' in copilot-vscode-features.md

Author: workwithbinu

docs/copilot/reference/copilot-vscode-features.md

@@ -54,7 +54,7 @@ Start a natural language chat conversation to get help with coding tasks. For ex
 | Context window control | Visual indicator in the chat input box showing [context window usage](/docs/copilot/chat/copilot-chat-context.md#monitor-context-window-usage). Hover for total token count and a breakdown by category. |
 | `Add Context...` | Attach different types of [context to your chat prompt](/docs/copilot/chat/copilot-chat-context.md). |
 | `/`-command | Use [slash commands](#slash-commands) for common tasks or invoke a [reusable chat prompt](/docs/copilot/customization/overview.md). |
-| `#`-mention | Reference common tools or chat variables to [provide context](/docs/copilot/chat/copilot-chat-context.md) within in your prompt. |
+| `#`-mention | Reference common tools or chat variables to [provide context](/docs/copilot/chat/copilot-chat-context.md) within your prompt. |
 | `@`-mention | Reference [chat participants](#chat-participants) to handle domain-specific requests. |
 | Edit (<i class="codicon codicon-pencil"></i>) | [Edit a previous chat prompt](/docs/copilot/chat/chat-checkpoints.md#edit-a-previous-chat-request) and revert changes. |
 | History (<i class="codicon codicon-history"></i>) | Access your history of chat sessions. |

release-notes/v1_73.md

@@ -255,7 +255,7 @@ Link occurrence highlighting in Markdown shows you all the places in the current
 
 ![Highlighting all occurrences of a link](images/1_73/md-link-highlight.png)
 
-Notice how with the cursor on the the first link in the document, all links to `First Header` as well as the header itself are highlighted in the document and in the gutter to the right of the document.
+Notice how with the cursor on the first link in the document, all links to `First Header` as well as the header itself are highlighted in the document and in the gutter to the right of the document.
 
 This feature is off by default. To enable it, turn on the `markdown.occurrencesHighlight.enabled` setting.
 

release-notes/v1_89.md

@@ -111,7 +111,7 @@ When enabled, the current theme is defined by the <code codesetting="workbench.p
 
 In that case, the <code codesetting="workbench.colorTheme">workbench.colorTheme</code> setting is then no longer considered. It is only used when <code codesetting="window.autoDetectColorScheme">window.autoDetectColorScheme</code> is off.
 
-In this milestone, what's new is that the theme picker dialog (**Preferences: Color Theme** command) is now aware of the system color mode. Notice how the theme selection only shows dark themes when the system in in dark mode:
+In this milestone, what's new is that the theme picker dialog (**Preferences: Color Theme** command) is now aware of the system color mode. Notice how the theme selection only shows dark themes when the system is in dark mode:
 
 ![Screenshot showing the theme selection dialog configuring the theme for Dark mode.](images/1_89/configuring_dark_mode.png)
 

release-notes/v1_91.md

@@ -156,7 +156,7 @@ The folding placeholder (ellipsis) can now be themed with the color `editor.fold
 
 With the <code codesetting="editor.codeActionsOnSave">editor.codeActionsOnSave</code> setting, you can configure a set of Code Actions that are automatically applied when you save a file, for example to organize imports. We improved the IntelliSense for configuring this setting by providing a list of available Code Actions based on your workspace files and the active extensions.
 
-> **Note**: be aware that that although `true` and `false` are still valid configurations at the moment, they will be deprecated in favor of `explicit`, `always`, and `never`. See [Code Actions on Save Docs](https://code.visualstudio.com/docs/typescript/typescript-refactoring#_code-actions-on-save) for examples.
+> **Note**: be aware that although `true` and `false` are still valid configurations at the moment, they will be deprecated in favor of `explicit`, `always`, and `never`. See [Code Actions on Save Docs](https://code.visualstudio.com/docs/typescript/typescript-refactoring#_code-actions-on-save) for examples.
 
 ### Quickly turn off read-only file status
 

release-notes/v1_96.md

@@ -625,7 +625,7 @@ You can view the full documentation in the [`chat-extension-utils` repository](h
 
 ### Attributable Coverage API
 
-The test coverage APIs now enable extensions to provide coverage information on a per-test basis. To implement this API, populate the the `includesTests?: TestItem[]` property on the `FileCoverage` to indicate which tests executed code in that file, and implement `TestRunProfile.loadDetailedCoverageForTest` to provide statement and declaration coverage.
+The test coverage APIs now enable extensions to provide coverage information on a per-test basis. To implement this API, populate the `includesTests?: TestItem[]` property on the `FileCoverage` to indicate which tests executed code in that file, and implement `TestRunProfile.loadDetailedCoverageForTest` to provide statement and declaration coverage.
 
 See the [Attributable Coverage section above](#attributable-coverage) for an example of what this looks like for users.
 

remote-release-notes/v1_53.md

@@ -49,11 +49,11 @@ Previously, after a short duration of failing to communicate with the remote, a
 
 ### Port attributes
 
-Attributes can now be configured for ports in settings. These attributes let you control the label that shows in the Ports view, the action that occurs when the port is autoforwarded, and whether that that port should always prompt for elevation if the local port is privileged (currently no Remote extensions support this last one).
+Attributes can now be configured for ports in settings. These attributes let you control the label that shows in the Ports view, the action that occurs when the port is autoforwarded, and whether that port should always prompt for elevation if the local port is privileged (currently no Remote extensions support this last one).
 
 * The port number can be a number or a range (ex. `3000` or `30000-40000`).
 * `label`: A label for the port in the "Ports" view.
-* `onAutoForward`: Specifies the action do be taken when the port is autoforwarded. See the setting `"remote.autoForwardPorts"` for more information about autoforwarding. Can be one of the following:
+* `onAutoForward`: Specifies the action to be taken when the port is autoforwarded. See the setting `"remote.autoForwardPorts"` for more information about autoforwarding. Can be one of the following:
   * `notify`: Shows a notification, default
   * `silent`: The port will be autoforwarded, but no notification will be shown
   * `openBrowser`: Immediately opens the browser when the port is autoforwarded