Linter fixed

Signed-off-by: Nico Vibert <nicolas.vibert@isovalent.com>
cilium · Jun 14, 2023 · 2980a31 · 2980a31
1 parent 2b9420e
commit 2980a31
Show file tree

Hide file tree

Showing 2 changed files with 8 additions and 6 deletions.
diff --git a/Documentation/network/servicemesh/ingress-to-gateway/http-migration.rst b/Documentation/network/servicemesh/ingress-to-gateway/http-migration.rst
@@ -10,10 +10,10 @@
 HTTP Migration Example
 **********************
 
-This example shows how to take an existing Ingress configuration and migrate it to the equivalent Gateway API resource.
+This example shows you how to migrate an existing Ingress configuration to the equivalent Gateway API resource.
 
-It uses the Cilium :ref:`gs_ingress_http` as the starting Ingress configuration. 
-The same approach will apply to other controllers, albeit each Ingress controller configuration varies.
+The Cilium :ref:`gs_ingress_http` serves as the starting Ingress configuration. 
+The same approach applies to other controllers, though each Ingress controller configuration varies.
 
 The example Ingress configuration routes traffic to backend services from the
 ``bookinfo`` demo microservices app from the Istio project.

diff --git a/Documentation/network/servicemesh/ingress-to-gateway/ingress-to-gateway.rst b/Documentation/network/servicemesh/ingress-to-gateway/ingress-to-gateway.rst
@@ -37,11 +37,11 @@ created inconsistencies from one Ingress Controller to another. For example, iss
 Finally, the Ingress API suffers from operational constraints: it is not well suited for multi-team clusters with shared load-balancing infrastructure.
 
 Benefits of the Gateway API
-#######################
+###########################
 
-The Gateway API was designed to address the limitations of Ingress API. The [Kubernetes SIG-Network](https://github.com/kubernetes/community/tree/master/sig-network) team designs and maintains the Gateway API.
+The Gateway API was designed to address the limitations of Ingress API. The `Kubernetes SIG-Network <https://github.com/kubernetes/community/tree/master/sig-network>`_ team designs and maintains the Gateway API.
 
-For more information about the Gateway API, see `the Gateway API project page<https://gateway-api.sigs.k8s.io/>`_.
+For more information about the Gateway API, see `the Gateway API project page <https://gateway-api.sigs.k8s.io/>`_.
 
 The Gateway API provides a centralized mechanism for managing and enforcing policies for external traffic, 
 including HTTP routing, TLS termination, traffic splitting/weighting, and header modification.
@@ -73,7 +73,9 @@ There are two primary methods to migrate Ingress API resources to Gateway API:
 - *manual*: manually creating Gateway API resources based on existing Ingress API resources.
 - *automated*: creating rules using the `ingress2gateway tool <https://github.com/kubernetes-sigs/ingress2gateway>`_. 
   The ingress2gateway project reads Ingress resources from a Kubernetes cluster based on your current Kube Config. It outputs YAML for equivalent Gateway API resources to stdout.
+
 .. note::
+
     The ``ingress2gateway`` tool remains experimental and is not recommended for production.
 
 Ingress Annotations Migration