chore: add inclusive terminology scan and error fixes

* chore: add inclusive terminology scan and error fixes

Signed-off-by: Ani Brahmamurthy <[email protected]>

.github/workflows/ci.yaml

@@ -20,6 +20,11 @@ jobs:
         go-version: 1.18.x
     - name: Test
       run: go test ./... -coverprofile cover.out
+    - name: Scan Inclusive Terminology
+      uses: get-woke/woke-action@v0
+      with: 
+        fail-on-error: true
+        woke-args: -c https://via.vmw.com/its-woke-rules
     - name: Upload coverage to Codecov
       uses: codecov/codecov-action@v3
 
@@ -183,7 +188,7 @@ jobs:
         docker network connect kind local-registry
 
         # Document the local registry
-        # https://github.com/kubernetes/enhancements/tree/master/keps/sig-cluster-lifecycle/generic/1755-communicating-a-local-registry
+        # https://github.com/kubernetes/enhancements/tree/master/keps/sig-cluster-lifecycle/generic/1755-communicating-a-local-registry # wokeignore:rule=master
         cat <<EOF | kubectl apply -f -
         apiVersion: v1
         kind: ConfigMap

.wokeignore

@@ -0,0 +1,2 @@
+**/go.mod
+**/go.sum

CONTRIBUTING.md

@@ -17,19 +17,19 @@ Example:
 
 ``` shell
 git remote add upstream https://github.com/vmware/service-bindings.git
-git checkout -b my-new-feature master
+git checkout -b my-new-feature main
 git commit -a
 git push origin my-new-feature
 ```
 
 ### Staying In Sync With Upstream
 
-When your branch gets out of sync with the vmware/master branch, use the following to update:
+When your branch gets out of sync with the vmware/main branch, use the following to update:
 
 ``` shell
 git checkout my-new-feature
 git fetch -a
-git pull --rebase upstream master
+git pull --rebase upstream main
 git push --force-with-lease origin my-new-feature
 ```
 
@@ -52,7 +52,7 @@ If you need to squash changes into an earlier commit, you can use:
 ``` shell
 git add .
 git commit --fixup <commit>
-git rebase -i --autosquash master
+git rebase -i --autosquash main
 git push --force-with-lease origin my-new-feature
 ```
 
@@ -66,6 +66,7 @@ notification when you git push.
 We follow the conventions on [How to Write a Git Commit Message](http://chris.beams.io/posts/git-commit/).
 
 Be sure to include any related GitHub issue references in the commit message.  See
+<!-- wokeignore:rule=master -->
 [GFM syntax](https://guides.github.com/features/mastering-markdown/#GitHub-flavored-markdown) for referencing issues
 and commits.