Update spellcheck GH Action to the latest (#101)

Sync the config as well

Signed-off-by: Tim Smith <[email protected]>

.github/actions/spelling/expect.txt

@@ -2,6 +2,9 @@ Adddays
 bigquery
 cea
 CUSTOMERID
+linux
 mpim
+openssh
 saas
+spdx
 xoxp

.github/actions/spelling/line_forbidden.patterns

@@ -1,4 +1,4 @@
-# Detect common combinations of valid words that are in fact invalid. 
+# Detect common combinations of valid words that are in fact invalid.
 # Useful for brand capitalizations
 
 #
@@ -9,6 +9,10 @@
 \sthe Mondoo Platform\b
 \sMondoo platform\b
 
+# s.b. Compliance Hub
+\scompliance hub\b
+\sCompliance hubplatform\b
+
 #
 # Industry Terms
 #
@@ -50,7 +54,7 @@
 # s.b. MariaDB
 \bMaria DB\b
 \bmariaDB\b
-\bmariaDb\b
+# \bmariaDb\b causes failures in MQL queries
 
 # s.b. PostgreSQL
 \bPostgreSql\b
@@ -98,6 +102,7 @@
 
 # s.b. Red Hat
 \bRedHat\b
+\bRedhat\b
 
 # s.b. AlmaLinux
 \bAlma Linux\b

.github/actions/spelling/reject.txt

@@ -10,4 +10,3 @@ Sorce
 ^untilling$
 ^wether.*
 \w*(?<!right-)click
-press

.github/dependabot.yml

@@ -1,3 +1,4 @@
+---
 version: 2
 updates:
   - package-ecosystem: "github-actions"

.github/workflows/spell-check.yaml

@@ -23,12 +23,12 @@ jobs:
     steps:
       - name: check-spelling
         id: spelling
-        uses: check-spelling/[email protected].21
+        uses: check-spelling/[email protected].22
         with:
           suppress_push_for_open_pull_request: 1
           checkout: true
           post_comment: 0
-          dictionary_source_prefixes: '{"mondoo": "https://raw.githubusercontent.com/mondoohq/spellcheck-dictionary/main/", "cspell": "https://raw.githubusercontent.com/check-spelling/cspell-dicts/v20220816/dictionaries/"}'
+          dictionary_source_prefixes: '{"mondoo": "https://raw.githubusercontent.com/mondoohq/spellcheck-dictionary/main/", "cspell": "https://raw.githubusercontent.com/check-spelling/cspell-dicts/v20230509/dictionaries/"}'
           extra_dictionaries:
             cspell:aws/aws.txt
             cspell:filetypes/filetypes.txt
@@ -47,7 +47,7 @@ jobs:
     if: (success() || failure()) && needs.spelling.outputs.followup
     steps:
       - name: comment
-        uses: check-spelling/[email protected].21
+        uses: check-spelling/[email protected].22
         with:
           checkout: true
           task: ${{ needs.spelling.outputs.followup }}

README.md

@@ -3,7 +3,7 @@
 This project contains inventory and incident response query packs for [`cnquery`](https://github.com/mondoohq/cnquery). We've organized them into these directories:
 
 - [core](core) - Core packs contain baseline queries such as incident response probes for different targets. Core query packs are maintained by Mondoo and have strict quality requirements.
-- [extra](extra) - Extra packs are are a mix of community- and Mondoo-maintained queries that are outside Mondoo's core support tier.
+- [extra](extra) - Extra packs are a mix of community- and Mondoo-maintained queries that are outside Mondoo's core support tier.
 - [community](community) - Community packs are primarily maintained by the community with support from the Mondoo team. Community packs may move to extra or core over time.
 
 ## Join the community!

extra/mondoo-googleworkplace-incident-response.mql.yaml

@@ -22,7 +22,7 @@ packs:
 
         1. Create/Select a GCP project
         2. Navigate to the [Google API Console](https://console.cloud.google.com/apis/dashboard). 
-        3. Click "Enable APIs and Services" and enable the following APIs:
+        3. Select "Enable APIs and Services" and enable the following APIs:
           - Admin SDK API 
           - Cloud Identity API 
           - Google Calendar API
@@ -31,7 +31,7 @@ packs:
           - Google People API
         4. Create a service account for [Google Workspace](https://support.google.com/a/answer/7378726?product_name=UnuFlow&hl=en&visit_id=638041387835615758-4147680582&rd=1&src=supportwidget0&hl=en)
         5. Create credentials for the service account and download the json file
-        6. Enter the following scopes in Security -> Access and data controls -> API controls, and click on  [Domain-wide Delegation](https://developers.google.com/workspace/guides/create-credentials#delegate_domain-wide_authority_to_your_service_account) 
+        6. Enter the following scopes in Security -> Access and data controls -> API controls, and select [Domain-wide Delegation](https://developers.google.com/workspace/guides/create-credentials#delegate_domain-wide_authority_to_your_service_account) 
 
           - https://www.googleapis.com/auth/admin.chrome.printers.readonly
           - https://www.googleapis.com/auth/admin.directory.customer.readonly

extra/mondoo-slack-incident-response.mql.yaml

@@ -24,10 +24,10 @@ packs:
         and assign the appropriate permissions:
 
         1. Sign in to [the Slack website](https://api.slack.com/apps/), and view "Your Apps"
-        2. Click "Create New App"
+        2. Select "Create New App"
         3. Select "From scratch"
-        4. Enter an "App Name" e.g. cnquery and select the workspace, then click "Create App"
-        5. In the section "Add features & functionality" click on "Permissions"
+        4. Enter an "App Name" e.g. cnquery and select the workspace, then select "Create App"
+        5. In the section "Add features & functionality" select "Permissions"
         6. Scroll to "Scopes" and then "User Token Scopes"
  
         Note: Bots are very limited in their access; therefore we need to set the user scopes
@@ -44,7 +44,7 @@ packs:
         | [usergroups:read](https://api.slack.com/scopes/usergroups:read) | 
         | [users:read](https://api.slack.com/scopes/users:read) |
 
-        8. Scroll up to "OAuth Tokens for Your Workspace" and click "Install to Workspace"
+        8. Scroll up to "OAuth Tokens for Your Workspace" and select "Install to Workspace"
         9. Copy the provided "User OAuth Token", it will look like `xoxp-1234567890123-1234567890123-1234567890123-12345cea5ae0d3bed30dca43cb34c2d1`
 
         ### Run query pack