chore: fix spelling

Author: jbampton

core/nodejs10Action/Dockerfile

@@ -26,7 +26,7 @@ RUN apt-get update && apt-get install -y \
  && rm -rf /var/lib/apt/lists/*
 
 # Add sources and copy the package.json to root container,
-# so npm packages from user functions take precendence.
+# so npm packages from user functions take precedence.
 #
 WORKDIR /nodejsAction
 ADD . /nodejsAction/

core/nodejs12Action/Dockerfile

@@ -26,7 +26,7 @@ RUN apt-get update && apt-get install -y \
  && rm -rf /var/lib/apt/lists/*
 
 # Add sources and copy the package.json to root container,
-# so npm packages from user functions take precendence.
+# so npm packages from user functions take precedence.
 #
 WORKDIR /nodejsAction
 ADD . /nodejsAction/

core/nodejs14Action/Dockerfile

@@ -26,7 +26,7 @@ RUN apt-get update && apt-get install -y \
  && rm -rf /var/lib/apt/lists/*
 
 # Add sources and copy the package.json to root container,
-# so npm packages from user functions take precendence.
+# so npm packages from user functions take precedence.
 #
 WORKDIR /nodejsAction
 ADD . /nodejsAction/

core/nodejsActionBase/Dockerfile

@@ -26,7 +26,7 @@ RUN apt-get update && apt-get install -y \
  && rm -rf /var/lib/apt/lists/*
 
 # Add sources and copy the package.json to root container,
-# so npm packages from user functions take precendence.
+# so npm packages from user functions take precedence.
 #
 ADD . /nodejsAction/
 COPY package.json /

core/typescript37Action/Dockerfile

@@ -59,7 +59,7 @@ COPY --from=builder_release /bin/proxy /bin/proxy_release
 RUN mv /bin/proxy_${GO_PROXY_BUILD_FROM} /bin/proxy
 
 # Add sources and copy the package.json to root container,
-# so npm packages from user functions take precendence.
+# so npm packages from user functions take precedence.
 #
 WORKDIR /app
 COPY bin/compile /bin/compile

docs/users/knative-build.md

@@ -157,7 +157,7 @@ status:
 
 # Building and Serving OpenWhisk Runtime Build Templates
 
-All OpenWhisk Runtime Build Templates require a valid Kubernetes **Service Account** with access to a Kubernetes **Secret** that containst base64 encoded versions of your Docker Hub username and password. This credential will be used as part of the Knative Build process to "push" your Knative application image containing your OpenWhisk Action to Docker Hub.
+All OpenWhisk Runtime Build Templates require a valid Kubernetes **Service Account** with access to a Kubernetes **Secret** that contains base64 encoded versions of your Docker Hub username and password. This credential will be used as part of the Knative Build process to "push" your Knative application image containing your OpenWhisk Action to Docker Hub.
 
 ## Clone this repository
 
@@ -472,7 +472,7 @@ curl -H "Host: nodejs-helloworld.default.example.com" -X POST http://${IP_ADDRES
 
 #### PROBLEM: Kubernetes default namespace does not have "istio-injection: enabled" key-value
 
-If the `default` namespace does not have this value under the `metadata` section, you may have forgotton to issue the following command as part of the Knative setup:
+If the `default` namespace does not have this value under the `metadata` section, you may have forgotten to issue the following command as part of the Knative setup:
 
 ```bash
 $ kubectl label namespace default istio-injection=enabled

tests/src/test/knative/README.md

@@ -212,10 +212,10 @@ be provided by a control-plane which would manage pools of the runtimes and trac
 
 ## Running with OW_RUNTIME_PLATFORM set to "openwhisk"
 
-The standard OW methods used to run functions is done through calls to 2 separte endpoints.
+The standard OW methods used to run functions is done through calls to 2 separate endpoints.
 In short, The control plane would:
 
-1. first, invoke the */init* route with strictly the OW "init. data" (JSON format) including the funtional
+1. first, invoke the */init* route with strictly the OW "init. data" (JSON format) including the functional
 code itself.
 2. then, invoke */run* route which executes the function (i.e., Activates the function) with caller-provided
 parameters via OW "value data" (JSON format) along with per-activation information which would normally be