fix: typo (#7786)

* fix: typo

* fix: typo

api/extension-guides/debugger-extension.md

@@ -165,7 +165,7 @@ about this can be found [here](https://microsoft.github.io/debug-adapter-protoco
 
 ## Anatomy of the package.json of a Debugger Extension
 
-Besides providing a debugger-specific implementation of the debug adapter a debugger extension needs a `package.json` that contributes to the various debug-related contributions points.
+Besides providing a debugger-specific implementation of the debug adapter a debugger extension needs a `package.json` that contributes to the various debug-related contribution points.
 
 So let's have a closer look at the `package.json` of Mock Debug.
 
@@ -258,7 +258,7 @@ First, we use the **breakpoints** contribution point to list the languages for w
 Next is the **debuggers** section. Here, one debugger is introduced under a debug **type** `mock`. The user can reference this type in launch configurations. The optional attribute **label** can be used to give the debug type a nice name when showing it in the UI.
 
 Since the debug extension uses a debug adapter, a relative path to its code is given as the **program** attribute.
-In order to make the extension self-contained the application must live inside the extension folder. By convention, we keep this applications inside a folder named `out` or `bin`, but you are free to use a different name.
+In order to make the extension self-contained the application must live inside the extension folder. By convention, we keep this application inside a folder named `out` or `bin`, but you are free to use a different name.
 
 Since VS Code runs on different platforms, we have to make sure that the DA program supports the different platforms as well. For this we have the following options: