Introduce inclusive naming check and update existing language

We are following the Inclusive Naming Initiative's guidance as that is what the
CNCF supports.

.github/workflows/inclusive-language-check.yml

@@ -0,0 +1,10 @@
+---
+name: Check inclusive language
+
+on:
+  pull_request:
+    types: ['opened', 'reopened']
+
+jobs:
+  check-inclusive-language:
+    uses: vmware-tanzu/carvel-release-scripts/.github/workflows/inclusive-language-check.yml@main

.wokeignore

@@ -0,0 +1,2 @@
+# out of our control
+site/content/blog/argocd-carvel-plugin.md

site/content/blog/carvel-vcluster.md

@@ -134,7 +134,7 @@ $ kapp deploy -a simple-app -f https://raw.githubusercontent.com/vmware-tanzu/ca
 
 Type in `y` to confirm you would like to deploy the Carvel sample app to the vcluster. 
 
-Once the deployment is successful, let's do another sanity check and see what apps exist on the host cluster:
+Once the deployment is successful, let's do another confidence check and see what apps exist on the host cluster:
 
 ```
 $ kapp ls 

site/content/ytt/docs/develop/how-it-works.md

@@ -157,7 +157,7 @@ They customize the result by supplying their situation-specific settings for Dat
 
 Let's explore what happens at each step in the pipeline.
 
-As the first pipeline step (black box) shows, [above](#the-ytt-pipeline) :
+As the first pipeline step (black box) shows, [above](#the-ytt-pipeline) : <!-- wokeignore:rule=blackbox -->
 
 1. process all the "Data Values Schema" documents (light grey input) — evaluating any templating in them;
 2. merge those documents, [in order](lang-ref-ytt-schema.md#multiple-schema-documents), generating a "Data Values Schema" document populated with default values and type information.

site/content/ytt/docs/v0.41.0/how-it-works.md

@@ -158,7 +158,7 @@ They customize the result by supplying their situation-specific settings for Dat
 
 Let's explore what happens at each step in the pipeline.
 
-As the first pipeline step (black box) shows, [above](#the-ytt-pipeline) :
+As the first pipeline step (black box) shows, [above](#the-ytt-pipeline) : <!-- wokeignore:rule=blackbox -->
 
 1. process all the "Data Values Schema" documents (light grey input) — evaluating any templating in them;
 2. merge those documents, [in order](lang-ref-ytt-schema.md#multiple-schema-documents), generating a "Data Values Schema" document populated with default values and type information.

site/content/ytt/docs/v0.42.0/how-it-works.md

@@ -158,7 +158,7 @@ They customize the result by supplying their situation-specific settings for Dat
 
 Let's explore what happens at each step in the pipeline.
 
-As the first pipeline step (black box) shows, [above](#the-ytt-pipeline) :
+As the first pipeline step (black box) shows, [above](#the-ytt-pipeline) : <!-- wokeignore:rule=blackbox -->
 
 1. process all the "Data Values Schema" documents (light grey input) — evaluating any templating in them;
 2. merge those documents, [in order](lang-ref-ytt-schema.md#multiple-schema-documents), generating a "Data Values Schema" document populated with default values and type information.

site/content/ytt/docs/v0.43.0/how-it-works.md

@@ -158,7 +158,7 @@ They customize the result by supplying their situation-specific settings for Dat
 
 Let's explore what happens at each step in the pipeline.
 
-As the first pipeline step (black box) shows, [above](#the-ytt-pipeline) :
+As the first pipeline step (black box) shows, [above](#the-ytt-pipeline) : <!-- wokeignore:rule=blackbox -->
 
 1. process all the "Data Values Schema" documents (light grey input) — evaluating any templating in them;
 2. merge those documents, [in order](lang-ref-ytt-schema.md#multiple-schema-documents), generating a "Data Values Schema" document populated with default values and type information.

site/content/ytt/js/deps.js

@@ -6500,7 +6500,7 @@
     e.dataTransfer.setData("Text", cm.getSelection());
     e.dataTransfer.effectAllowed = "copyMove";
 
-    // Use dummy image instead of default browsers image.
+    // Use placeholder image instead of default browsers image.
     // Recent Safari (~6.0.2) have a tendency to segfault when this happens, so we don't do it there.
     if (e.dataTransfer.setDragImage && !safari) {
       var img = elt("img", null, null, "position: fixed; left: 0; top: 0;");