[enterprise-4.8] SRVKS-814: Remove deprecated docs

_topic_map.yml

@@ -3071,8 +3071,6 @@ Topics:
     File: serverless-ossm-with-kourier-jwt
   - Name: Configuring a custom domain for a Knative service
     File: serverless-custom-domains
-  - Name: Configuring TLS for a custom domain using Kourier
-    File: serverless-ossm-tls-with-kourier
   - Name: Using a custom TLS certificate for domain mapping
     File: serverless-custom-tls-cert-domain-mapping
 #

modules/knative-service-cluster-local.adoc

@@ -1,5 +1,5 @@
 [id="knative-service-cluster-local_{context}"]
-= Setting cluster availability to `cluster-local`
+= Setting cluster availability to cluster local
 
 By default, Knative services are published to a public IP address.
 Being published to a public IP address means that Knative services are public applications, and have a publicly accessible URL.
@@ -19,7 +19,6 @@ For {ServerlessProductName} 1.15.0 and newer versions, the `serving.knative.dev/
 
 * Set the visibility for your service by adding the `networking.knative.dev/visibility=cluster-local` label:
 +
-
 [source,terminal]
 ----
 $ oc label ksvc <service_name> networking.knative.dev/visibility=cluster-local
@@ -29,14 +28,11 @@ $ oc label ksvc <service_name> networking.knative.dev/visibility=cluster-local
 
 * Check that the URL for your service is now in the format `\http://<service_name>.<namespace>.svc.cluster.local`, by entering the following command and reviewing the output:
 +
-
 [source,termina]
 ----
 $ oc get ksvc
 ----
-
 +
-
 .Example output
 [source,terminal]
 ----