Use correct TS setting name

Author: gregvanl

release-notes/v1_63.md

@@ -416,14 +416,14 @@ vscode.commands.executeCommand<vscode.CallHierarchyItem | undefined>('vscode.pre
 
 This change only effects the typings of `executeCommand` and does not change the behavior of this function.
 
-### Updating vscode.d.ts for strictOptionalProperties
+### Updating vscode.d.ts for exactOptionalPropertyTypes
 
-We've updated the typings in `vscode.d.ts` to better support TypeScript's [`strictOptionalProperties` strictness option](https://github.com/microsoft/TypeScript/pull/43947). This work included:
+We've updated the typings in `vscode.d.ts` to better support TypeScript's [`exactOptionalPropertyTypes` strictness option](https://www.typescriptlang.org/tsconfig#exactOptionalPropertyTypes). This work included:
 
 * Clarifying which optional properties can be assigned `undefined`.
 * Being more consistent in how we use `?` versus `| undefined`.
 
-If you are using `strictOptionalProperties` with your extension, please let us know if you run into any issues with the `vscode.d.ts` typings.
+If you are using `exactOptionalPropertyTypes` with your extension, please let us know if you run into any issues with the `vscode.d.ts` typings.
 
 ### HTML custom data from URIs