address review comments

Author: matthewbastien

userdocs/userdocs.docc/Articles/Advanced/install-pre-release.md

@@ -1,6 +1,6 @@
 # Installing Pre-Release Builds
 
-Live on the bleeding edge by switching to the pre-release version.
+Try out the latest updates by switching to the pre-release version.
 
 The Swift extension provides pre-release builds that can be used to test out unreleased features or get bug fixes before an official release can be published. Pre-release build numbers are always one minor version ahead of the most recent release.
 

userdocs/userdocs.docc/Articles/Features/language-features.md

@@ -2,4 +2,12 @@
 
 Language features to help you write Swift code.
 
-The Swift extension provides language features such as code completion and jump to definition via [SourceKit-LSP](https://github.com/apple/sourcekit-lsp). To ensure the extension functions correctly, it’s important to first build the project so that SourceKit-LSP has access to all the symbol data. Whenever you add a new dependency to your project, make sure to rebuild it so that SourceKit-LSP can update its information.
+> 💡 Tip: Language features are common to all VS Code extensions. See the [VS Code documentation about navigating code](https://code.visualstudio.com/docs/editing/editingevolved) for a more in-depth overview.
+
+The Swift extension provides language features such as code completion and jump to definition via [SourceKit-LSP](https://github.com/apple/sourcekit-lsp).
+
+> ⚠️ Important: With Swift toolchains prior to 6.1 you will need to build your project at least once for SourceKit-LSP to function correcly. Whenever you add a new dependency to your project, make sure to rebuild it so that SourceKit-LSP can update its information.
+
+SourceKit-LSP provides background indexing in Swift toolchain 6.1 which will automatically index your project on startup. All indexing results are cached in the `.build/index-build` folder within your workspace.
+
+SourceKit-LSP can be configured via extension settings. See <doc:settings> for more information.

userdocs/userdocs.docc/Articles/Features/project-view.md

@@ -1,6 +1,6 @@
 # Swift Project View
 
-View aspects of your Swift project at a glance.
+Navigate your Swift project.
 
 If your workspace contains a package, this extension will add a **Swift Project** view to the Explorer:
 

userdocs/userdocs.docc/Articles/Features/test-explorer.md

@@ -2,7 +2,7 @@
 
 vscode-swift shows test results in the test explorer.
 
-> 💡 Tip: The Test Explorer UI is common to all VS Code extensions. See the [VS Code documentation about testing](https://code.visualstudio.com/docs/debugtest/testing) for a more in-depth overview.
+> 💡 Tip: The Testing view is common to all VS Code extensions. See the [VS Code documentation about testing](https://code.visualstudio.com/docs/debugtest/testing) for a more in-depth overview.
 
 If your package contains tests then they can be viewed, run and debugged in the Test Explorer.
 

userdocs/userdocs.docc/Articles/Reference/commands.md

@@ -4,7 +4,7 @@ Useful VS Code commands added by the Swift extension.
 
 > 💡 Tip: Commands can be accessed from the VS Code command palette which is common to all VS Code extensions. See the [VS Code documentation about the command palette](https://code.visualstudio.com/docs/getstarted/userinterface#_command-palette) for a more in-depth overview.
 
-The Swift extension adds the following commands, each prefixed with `"Swift: "` in the UI.
+The Swift extension adds the following commands, each prefixed with `"Swift: "` in the command palette.
 
 #### Configuration
 
@@ -14,14 +14,14 @@ The Swift extension adds the following commands, each prefixed with `"Swift: "`
 
 The following command is only available on macOS:
 
-- **`Select Target Platform...`** - An experimental command that offers code completion for iOS and tvOS projects.
+- **`Select Target Platform...`** - An experimental command available in Swift 6.1 that offers code completion for iOS, tvOS, watchOS, and visionOS projects.
 
 #### Building and Debugging
 
 - **`Run Build`** - Run `swift build` for the package associated with the open file.
 - **`Debug Build`** - Run `swift build` with debugging enabled for the package associated with the open file, launching the binary and attaching the debugger.
 - **`Attach to Process...`** - Attach the debugger to an already running process for debugging.
-- **`Clean Build Folder`** - Clean the build folder for the package associated with the open file, removing all previously built products.
+- **`Clean Build Folder`** - Clean the `.build` folder for the package associated with the open file, removing all previously built products.
 
 #### Dependency Management
 

userdocs/userdocs.docc/Articles/Reference/settings.md

@@ -2,7 +2,7 @@
 
 vscode-swift provides various settings to configure its behaviour.
 
-> 💡 Tip: The Settings UI is common to all VS Code extensions. See the [VS Code documentation about personalizing VS Code](https://code.visualstudio.com/docs/getstarted/personalize-vscode) for a more in-depth overview.
+> 💡 Tip: The Settings Editor is common to all VS Code extensions. See the [documentation about personalizing VS Code](https://code.visualstudio.com/docs/getstarted/personalize-vscode) for a more in-depth overview.
 
 The Swift extension comes with a number of settings you can use to control how it works. Detailed descriptions of each setting are provided in the extension settings page.