directory confusion missing readinessProbe config

docs/serving/knative-kubernetes-services.md

@@ -31,7 +31,6 @@ that are active when running Knative Serving.
    webhook             ClusterIP   10.107.144.50    <none>        443/TCP                  1h
    ```
 
-````
  3. To view the deployments in your cluster, use the following command:
 
     ```sh
@@ -41,14 +40,14 @@ that are active when running Knative Serving.
     This should return the following output:
 
      ```sh
-NAME                     DESIRED   CURRENT   UP-TO-DATE   AVAILABLE   AGE
-activator                1         1         1            1           1h
-autoscaler               1         1         1            1           1h
-controller               1         1         1            1           1h
-networking-certmanager   1         1         1            1           1h
-networking-istio         1         1         1            1           1h
-webhook                  1         1         1            1           1h
-````
+     NAME                     DESIRED   CURRENT   UP-TO-DATE   AVAILABLE   AGE
+     activator                1         1         1            1           1h
+     autoscaler               1         1         1            1           1h
+     controller               1         1         1            1           1h
+     networking-certmanager   1         1         1            1           1h
+     networking-istio         1         1         1            1           1h
+     webhook                  1         1         1            1           1h
+     ```
 
 These services and deployments are installed by the `serving.yaml` file during
 install. The next section describes their function.

docs/serving/samples/rest-api-go/README.md

@@ -25,7 +25,7 @@ like `AAPL`,`AMZN`, `GOOG`, `MSFT`, etc.
 
    ```shell
    git clone -b "{{< branch >}}" https://github.com/knative/docs knative-docs
-   cd knative-docs/serving/samples/rest-api-go
+   cd knative-docs
    ```
 
 ## Setup
@@ -37,22 +37,17 @@ This sample uses Docker for both building and pushing.
 
 To build and push to a container registry using Docker:
 
-1. Move into the sample directory:
-
-   ```shell
-   cd $GOPATH/src/github.com/knative/docs
-   ```
-
-2. Set your preferred container registry endpoint as an environment variable.
+1. From the `knative-docs` directory, run the following command to set your 
+   container registry endpoint as an environment variable.
+
    This sample uses
    [Google Container Registry (GCR)](https://cloud.google.com/container-registry/):
-
-
+
     ```shell
     export REPO="gcr.io/<YOUR_PROJECT_ID>"
     ```
 
-3. Set up your container registry to make sure you are ready to push.
+1. Set up your container registry to make sure you are ready to push.
 
    To push to GCR, you need to:
 
@@ -67,21 +62,21 @@ To build and push to a container registry using Docker:
    If you are using a different container registry, you will want to follow the
    registry specific instructions for both setup and authorizing the image push.
 
-4. Use Docker to build your application container:
+1. Use Docker to build your application container:
 
    ```shell
    docker build \
      --tag "${REPO}/rest-api-go" \
      --file docs/serving/samples/rest-api-go/Dockerfile .
    ```
 
-5. Push your container to a container registry:
+1. Push your container to a container registry:
 
    ```shell
    docker push "${REPO}/rest-api-go"
    ```
 
-6. Substitute the image reference path in the template with our published image
+1. Substitute the image reference path in the template with our published image
    path. The command below substitutes using the \${REPO} variable into a new
    file called `docs/serving/samples/rest-api-go/sample.yaml`.
 

docs/serving/samples/rest-api-go/sample-template.yaml

@@ -29,3 +29,5 @@ spec:
             path: /
           initialDelaySeconds: 0
           periodSeconds: 3
+          timeoutSeconds: 11
+          failureThreshold: 3