Fix a couple of naming nits

github · Nov 11, 2022 · acbc6ca · acbc6ca
1 parent 84e5134
commit acbc6ca
Show file tree

Hide file tree

Showing 6 changed files with 14 additions and 14 deletions.
diff --git a/lib/analyze.js b/lib/analyze.js
diff --git a/lib/analyze.js.map b/lib/analyze.js.map
diff --git a/lib/codeql.js b/lib/codeql.js
diff --git a/lib/codeql.js.map b/lib/codeql.js.map
diff --git a/src/analyze.ts b/src/analyze.ts
@@ -235,7 +235,7 @@ export async function runQueries(
 
     try {
       if (await util.useCodeScanningConfigInCli(codeql, featureEnablement)) {
-        // If we are using the codescanning config in the CLI,
+        // If we are using the code scanning config in the CLI,
         // much of the work needed to generate the query suites
         // is done in the CLI. We just need to make a single
         // call to run all the queries for each language and

diff --git a/src/codeql.ts b/src/codeql.ts
@@ -821,7 +821,7 @@ async function getCodeQLForCmd(
           extraArgs.push(`--trace-process-name=${processName}`);
         } else {
           // We default to 3 if no other arguments are provided since this was the default
-          // behaviour of the Runner. Note this path never happens in the CodeQL Action
+          // behavior of the Runner. Note this path never happens in the CodeQL Action
           // because that always passes in a process name.
           extraArgs.push(`--trace-process-level=${processLevel || 3}`);
         }
@@ -849,7 +849,7 @@ async function getCodeQLForCmd(
         }
       }
 
-      const configLocation = await generateCodescanningConfig(
+      const configLocation = await generateCodeScanningConfig(
         codeql,
         config,
         featureEnablement
@@ -1186,8 +1186,8 @@ async function getCodeQLForCmd(
       await new toolrunner.ToolRunner(cmd, args).exec();
     },
   };
-  // To ensure that status reports include the CodeQL CLI version whereever
-  // possbile, we want to call getVersion(), which populates the version value
+  // To ensure that status reports include the CodeQL CLI version wherever
+  // possible, we want to call getVersion(), which populates the version value
   // used by status reporting, at the earliest opportunity. But invoking
   // getVersion() directly here breaks tests that only pretend to create a
   // CodeQL object. So instead we rely on the assumption that all non-test
@@ -1303,7 +1303,7 @@ async function runTool(cmd: string, args: string[] = []) {
  * @param config The configuration to use.
  * @returns the path to the generated user configuration file.
  */
-async function generateCodescanningConfig(
+async function generateCodeScanningConfig(
   codeql: CodeQL,
   config: Config,
   featureEnablement: FeatureEnablement