From 76a2915787ef92347063bd301ffcd32703b1d8d7 Mon Sep 17 00:00:00 2001 From: Michael Schurter Date: Wed, 26 Jun 2019 08:34:58 -0700 Subject: [PATCH] docs: small typo/wording fixes for envoy (#6018) --- website/source/docs/connect/proxies/envoy.md | 10 +++++----- 1 file changed, 5 insertions(+), 5 deletions(-) diff --git a/website/source/docs/connect/proxies/envoy.md b/website/source/docs/connect/proxies/envoy.md index d07109d3c..5095b695c 100644 --- a/website/source/docs/connect/proxies/envoy.md +++ b/website/source/docs/connect/proxies/envoy.md @@ -216,15 +216,15 @@ definition](/docs/connect/registration/service-registration.html) or ## Advanced Configuration -To support more flexibility when configuring Envoy, several "lower-level" options exist that -exist that require knowledge of Envoy's configuration format. -Many allow configuring a subsection of either the bootstrap or +To support more flexibility when configuring Envoy, several "lower-level" options exist +that require knowledge of Envoy's configuration format. +Many options allow configuring a subsection of either the bootstrap or dynamic configuration using your own custom protobuf config. We separate these into two sets, [Advanced Bootstrap Options](#advanced-bootstrap-options) and [Escape Hatch -Overrides](#escape-hatch-overrides). Both require writing Envoy config in it's -protobuf JSON encoding. Advanced options are smaller chunks that might +Overrides](#escape-hatch-overrides). Both require writing Envoy config in the +protobuf JSON encoding. Advanced options cover smaller chunks that might commonly need to be set for tasks like configuring tracing. In contrast, escape hatches give almost complete control over the proxy setup, but require operators to manually code the entire configuration in protobuf JSON.