Fixes #3117 and broken links

docs/serving/_index.md

@@ -5,39 +5,37 @@ type: "docs"
 showlandingtoc: "false"
 ---
 
-Knative Serving builds on Kubernetes and Istio to support deploying and serving
-of serverless applications and functions. Serving is easy to get started with
-and scales to support advanced scenarios.
+Knative Serving builds on Kubernetes to support deploying and serving serverless applications and functions. Knative Serving is easy to get started with and scales to support advanced scenarios.
 
-The Knative Serving project provides middleware primitives that enable:
+The Knative Serving project provides middleware components that enable:
 
-- Rapid deployment of serverless containers
-- [Automatic scaling up and down to zero](./autoscaling/)
-- Routing and network programming for Istio components
-- Point-in-time snapshots of deployed code and configurations
+- Rapid deployment of serverless containers.
+- Autoscaling including scaling pods down to zero.
+- Support for multiple networking layers such as Ambassador, Courier, Gloo, Istio, and Kong, for integration into existing environments.
+- Point-in-time snapshots of deployed code and configurations.
 
 ## Serving resources
 
 Knative Serving defines a set of objects as Kubernetes Custom Resource
 Definitions (CRDs). These objects are used to define and control how your
 serverless workload behaves on the cluster:
 
-- [Service](https://github.com/knative/docs/blob/main/docs/serving/spec/knative-api-specification-1.0#service):
+- [Service](https://github.com/knative/specs/blob/main/specs/serving/knative-api-specification-1.0.md#service):
   The `service.serving.knative.dev` resource automatically manages the whole
   lifecycle of your workload. It controls the creation of other objects to
   ensure that your app has a route, a configuration, and a new revision for each
   update of the service. Service can be defined to always route traffic to the
   latest revision or to a pinned revision.
-- [Route](https://github.com/knative/docs/blob/main/docs/serving/spec/knative-api-specification-1.0#route):
+- [Route](https://github.com/knative/specs/blob/main/specs/serving/knative-api-specification-1.0.md#route):
   The `route.serving.knative.dev` resource maps a network endpoint to one or
   more revisions. You can manage the traffic in several ways, including
   fractional traffic and named routes.
-- [Configuration](https://github.com/knative/docs/blob/main/docs/serving/spec/knative-api-specification-1.0#configuration):
+- [Configuration](https://github.com/knative/specs/blob/main/specs/serving/knative-api-specification-1.0.md#configuration):
   The `configuration.serving.knative.dev` resource maintains the desired state
   for your deployment. It provides a clean separation between code and
   configuration and follows the Twelve-Factor App methodology. Modifying a
   configuration creates a new revision.
-- [Revision](https://github.com/knative/docs/blob/main/docs/serving/spec/knative-api-specification-1.0#revision):
+- [Revision](https://github.com/knative/specs/blob/main/specs/serving/knative-api-specification-1.0.md#revision):
   The `revision.serving.knative.dev` resource is a point-in-time snapshot of the
   code and configuration for each modification made to the workload. Revisions
   are immutable objects and can be retained for as long as useful. Knative
@@ -58,9 +56,7 @@ With the `Service` resource, a deployed service will automatically have a
 matching route and configuration created. Each time the `Service` is updated, a
 new revision is created.
 
-For more information on the resources and their interactions, see the
-[Resource Types Overview](https://github.com/knative/specs/blob/main/specs/serving/overview.md)
-in the Knative Serving repository.
+For more information on the resources and their interactions, see the [Resource Types Overview](https://github.com/knative/specs/blob/main/specs/serving/overview.md) in the Knative Serving repository.
 
 ## More samples and demos
 

docs/serving/debugging-application-issues.md

@@ -38,7 +38,7 @@ kubectl get route <route-name> --output yaml
 
 The `conditions` in `status` provide the reason if there is any failure. For
 details, see Knative
-[Error Conditions and Reporting](https://github.com/knative/docs/blob/main/docs/serving/spec/knative-api-specification-1.0.md#error-signalling).
+[Error Conditions and Reporting](https://github.com/knative/specs/blob/main/specs/serving/knative-api-specification-1.0.md#error-signalling).
 
 ### Check Ingress/Istio routing
 

docs/serving/deploying/private-registry.md

@@ -75,8 +75,7 @@ You need:
 
     Note: By default, the `default` service account in each of the
     [namespaces](https://kubernetes.io/docs/concepts/overview/working-with-objects/namespaces/)
-    of your Knative cluster are use by your revisions unless
-    [`serviceAccountName`](../spec/knative-api-specification-1.0) is specified.
+    of your Knative cluster are use by your revisions unless    [`serviceAccountName`](https://github.com/knative/specs/blob/main/specs/serving/knative-api-specification-1.0.md#revision-2) is specified.
 
    Run the following command to modify your `default` service account, assuming
    you named your secrets `container-registry`:
@@ -90,5 +89,4 @@ your credentials and have access to your container images in the private registr
 
 ## What's next
 
-You can now create a service that uses your container images from the private registry.
 [Learn how to create a Knative service](../getting-started-knative-app).