Review feedback

Author: BertanAygun

docs/extensibility/visualstudio.extensibility/get-started/in-proc-extensions.md

@@ -12,17 +12,17 @@ ms.technology: vs-ide-sdk
 
 # Using VisualStudio.Extensibility SDK and VSSDK together
 
-While the VisualStudio.Extensibility model was created primarily to host extensions outside of the devenv.exe process, it is possible to use VisualStudio.Extensibility SDK APIs in an extension running in Visual Studio process and utilizing traditional extensibility APIs provided by the [Microsoft.VisualStudio.Sdk](https://www.nuget.org/packages/Microsoft.VisualStudio.Sdk) packages.
+While the VisualStudio.Extensibility model was created primarily to host extensions outside of the devenv.exe process, it is possible to use VisualStudio.Extensibility SDK APIs in an extension running in the Visual Studio process and utilizing traditional extensibility APIs provided by the [Microsoft.VisualStudio.Sdk](https://www.nuget.org/packages/Microsoft.VisualStudio.Sdk) packages.
 
 The support of *in-proc* usage is meant to allow early adopters to the new VisualStudio.Extensibility APIs while relying on [Microsoft.VisualStudio.Sdk](https://www.nuget.org/packages/Microsoft.VisualStudio.Sdk) to cover any feature gap.
 
 This document is a quick walkthrough on different options to utilize VisualStudio.Extensibility SDK in-proc.
 
 * If you are developing a new extension, our recommended method is to create a VisualStudio.Extension that is hosted in-process following [this tutorial](#create-your-first-vssdk-compatible-visualstudioextensibility-extension). This will allow you to use full capabilities of VisualStudio.Extensibility SDK in addition to being able to inject VSSDK and MEF services.
 
-* If you have an existing VSSDK extension, you can follow [these tips](#use-visualstudioextensibility-apis-from-existing-vssdk-extensions) to use the new `VisualStudioExtensibility` instance in your extension.
+* If you have an existing VSSDK extension, you can follow [these tips](#use-visualstudioextensibility-apis-from-existing-vssdk-extensions) to use the new [VisualStudioExtensibility](https://learn.microsoft.com/en-us/dotnet/api/microsoft.visualstudio.extensibility.visualstudioextensibility) instance in your extension.
 
-* If you want to add commands, debug visualizers, tool windows to your existing VSSDK extension by using VisualStudio.Extensibility SDK, you can refer to [these tips](#using-visualstudioextensibility-sdk-and-vssdk-together) to host both a VSSDK extension and VisualStudio.Extensibility SDK in the same VS extension project.
+* If you want to add commands, debug visualizers, tool windows to your existing VSSDK extension by using the VisualStudio.Extensibility SDK, you can refer to [these tips](#add-a-visualstudioextensibility-extension-to-an-existing-vssdk-extension-project) to host both a VSSDK extension and a VisualStudio.Extensibility extension in the same VS extension project.
 
 # Create your first VSSDK-compatible VisualStudio.Extensibility extension
 
@@ -31,9 +31,8 @@ While the VisualStudio.Extensibility model was created primarily to host extensi
 
 ## Prerequisites
 
-* Visual Studio 2022.6 Preview 1 or higher with `.Net desktop development` workload. 
-* Install [VisualStudio.Extensibility Project System](https://marketplace.visualstudio.com/items?itemName=vsext.gladstone): This extension contains project templates for VisualStudio.Extensibility extensions.
-* If you're updating from earlier builds, make sure to update VisualStudio.Extensibility Project System to latest version as there are breaking changes in VisualStudio.Extensibility packages.
+* Visual Studio 2022.9 Preview 1 or higher with `.Net desktop development` and `Visual Studio extension development` workload. 
+* If you're updating from earlier builds, make sure to uninstall VisualStudio.Extensibility Project System to avoid potential conflicts.
 
 ## Create the extension project
 
@@ -124,9 +123,9 @@ internal class MyExtension : Extension
 
 # Use VisualStudio.Extensibility from existing VSSDK extensions
 
-For existing VSSDK extension, another option is to query for `VisualStudioExtensibility` instance via service provider and utilize its methods. This method will allow you to use new API surface area of VisualStudio.Extensibility SDK in your existing components. This can be useful in situations where you like to use the new API to query project information, document management without creating a new VisualStudio.Extensibility based extension. 
+For existing VSSDK extensions, another option is to query for the [VisualStudioExtensibility](https://learn.microsoft.com/en-us/dotnet/api/microsoft.visualstudio.extensibility.visualstudioextensibility) instance via service provider and utilize its methods. This method will allow you to use new the API surface area of VisualStudio.Extensibility SDK in your existing components. This can be useful in situations where you like to use the new API to query project information, document management without creating a new VisualStudio.Extensibility based extension. 
 
-Here is an example code snippet that shows how one can utilize `VisualStudioExtensibility` with in a VSSDK package:
+Here is an example code snippet that shows how one can utilize `VisualStudioExtensibility` within a VSSDK package:
 
 * In your `.csproj` include a package reference to VisualStudio.Extensibility APIs:
 
@@ -154,9 +153,9 @@ public class VSSDKPackage : AsyncPackage
 }
 ```
 
-# Add VisualStudio.Extensibility extension in to an existing VSSDK extension project
+# Add a VisualStudio.Extensibility extension to an existing VSSDK extension project
 
-If you also want to contribute components like tool windows, editor listeners using VisualStudio.Extensibility SDK within your existing VSSDK extension, you will have to follow additional steps to create a VisualStudio.Extensibility `Extension` instance in your project.
+If you also want to contribute components like tool windows, editor listeners using the VisualStudio.Extensibility SDK within your existing VSSDK extension, you will have to follow additional steps to create a VisualStudio.Extensibility [Extension](https://learn.microsoft.com/en-us/dotnet/api/microsoft.visualstudio.extensibility.extension) instance in your project.
 
 * You will need an SDK style `.csproj` in order to utilize VisualStudio.Extensibility SDK packages. For existing projects, you may need to update your `.csproj` to an SDK style one.
 
@@ -167,7 +166,7 @@ If you also want to contribute components like tool windows, editor listeners us
     <PackageReference Include="Microsoft.VisualStudio.Extensibility.Build" Version="17.9.23-preview-1" />
 ```
 
-* Add `VssdkCompatibleExtension` property to your project file, setting it to `true`. This will disable `vsixmanifest` generation and enable some of VSSDK features for compatibility.
+* Add `VssdkCompatibleExtension` property to your project file, setting it to `true`. This property will enable some VSSDK features for compatibility.
 
 ```XML
 <PropertyGroup>