From fee96dcf10624098cec04079c281cb3288546325 Mon Sep 17 00:00:00 2001
From: Rachael Luo <67493131+RachaelLuo@users.noreply.github.com>
Date: Wed, 19 Oct 2022 22:46:51 +0800
Subject: [PATCH] fix route docs (#12121)

fix docs

fix route docs
---
 content/en/docs/concepts/traffic-management/index.md | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)

diff --git a/content/en/docs/concepts/traffic-management/index.md b/content/en/docs/concepts/traffic-management/index.md
index b42670b9c1..74c66344eb 100644
--- a/content/en/docs/concepts/traffic-management/index.md
+++ b/content/en/docs/concepts/traffic-management/index.md
@@ -110,7 +110,7 @@ traffic from your internal users to a particular set of instances.
 With a virtual service, you can specify traffic behavior for one or more hostnames.
 You use routing rules in the virtual service that tell Envoy how to send the
 virtual service’s traffic to appropriate destinations. Route destinations can
-be versions of the same service or entirely different services.
+be different versions of the same service or entirely different services.
 
 A typical use case is to send traffic to different versions of a service,
 specified as service subsets. Clients send requests to the virtual service host as if