chore: small typo

Author: AkatQuas

.continue/prompts/core-unit-test.prompt

@@ -4,7 +4,7 @@ description: Generate unit tests for core utilities
 Write jest tests for the provided code.
 Use jest version ^29 (e.g. jest 29.7.0)
 
-Use best practices. Be clear and consise.
+Use best practices. Be clear and concise.
 Aim for 100% code coverage where reasonable.
 Multiple tests can be written, split up tests for best clarity and readability.
 Only use typescript, and if the file/code is not typescript, warn the user.
@@ -15,7 +15,7 @@ Use double quotes (or backticks if needed) for strings
 The code being tested is used in IDE extensions, and it:
 - accesses code workspaces through the IDE ("workspace directories")
 - persists extension-related data to the the local machine of the user ("global directory"), and
-- uses configuration via a `ConfigHandler`, which is stored in either the global directory (default) or accesed via a remote "control plane" using the `ControlPlaneClient`
+- uses configuration via a `ConfigHandler`, which is stored in either the global directory (default) or accessed via a remote "control plane" using the `ControlPlaneClient`
 
 Jest testing setup includes
 - @core/test/jest.global-setup.ts initializes a temporary global directory, which is where files that store persisted extension data live.
@@ -31,7 +31,7 @@ Jest testing setup includes
 
 Do NOT write tests for any files in `core/test`, only use them as helpers for testing other files. If no other files are provided, warn the user and write no tests.
 
-IMPORTANT: Do NOT mock the fixtures above other than using `jest.spyOn`. DO mock 3rd party modules, etc. when sensible. 
+IMPORTANT: Do NOT mock the fixtures above other than using `jest.spyOn`. DO mock 3rd party modules, etc. when sensible.
 Instead, generate actual mock files and data for operations
 Pure mocks should only be used to emulate specific network responses/error or hard-to-duplicate errors, or to prevent long-duration tests