From 1b37179f2fa68a53f3c9fd2e9a1c0b16624717a0 Mon Sep 17 00:00:00 2001
From: "data-plane-api(CircleCI)" <data-plane-api@users.noreply.github.com>
Date: Mon, 6 Jul 2020 16:59:57 +0000
Subject: [PATCH] fix xds proto doc (#11882)

Signed-off-by: Rama Chavali <rama.rao@salesforce.com>

Mirrored from https://github.com/envoyproxy/envoy @ 889e4e4dbaebe1ad6c70d773536fb1a6a5752838
---
 xds_protocol.rst | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)

diff --git a/xds_protocol.rst b/xds_protocol.rst
index 6b580ad3..1b254ad7 100644
--- a/xds_protocol.rst
+++ b/xds_protocol.rst
@@ -77,7 +77,7 @@ API flow
 For typical HTTP routing scenarios, the core resource types for the client's configuration are
 `Listener`, `RouteConfiguration`, `Cluster`, and `ClusterLoadAssignment`. Each `Listener` resource
 may point to a `RouteConfiguration` resource, which may point to one or more `Cluster` resources,
-and each Cluster` resource may point to a `ClusterLoadAssignment` resource.
+and each `Cluster` resource may point to a `ClusterLoadAssignment` resource.
 
 Envoy fetches all `Listener` and `Cluster` resources at startup. It then fetches whatever
 `RouteConfiguration` and `ClusterLoadAssignment` resources that are required by the `Listener` and