From a3fe45f9e925cc2454478b55facb736091936bfc Mon Sep 17 00:00:00 2001 From: Steven Martin Date: Mon, 1 Jul 2024 15:49:43 -0400 Subject: [PATCH] docs: updates to networking reference --- docs/pages/reference/networking.mdx | 6 +++--- 1 file changed, 3 insertions(+), 3 deletions(-) diff --git a/docs/pages/reference/networking.mdx b/docs/pages/reference/networking.mdx index a21e3b46f8eeb..ec330b6685f11 100644 --- a/docs/pages/reference/networking.mdx +++ b/docs/pages/reference/networking.mdx @@ -69,7 +69,7 @@ environment variables when running Teleport. You can also optionally set the specified hosts/netmasks/ports. By default, Teleport installations based on package managers (such as `apt` and -`yum`) configure The `teleport` systemd unit to read environment variables from +`yum`) configure the `teleport` systemd unit to read environment variables from the file `/etc/default/teleport`. To configure HTTP CONNECT tunneling, you can assign these environment variables @@ -109,7 +109,7 @@ The value of `HTTPS_PROXY` or `HTTP_PROXY` should be in the format type="warning" title="Note" > - The proxy service also respects `HTTPS_PROXY` and `HTTP_PROXY` when connecting to a local kubernetes cluster, which may not work. To fix this, add `kube.teleport.cluster.local` to `NO_PROXY`. + The Proxy Service also respects `HTTPS_PROXY` and `HTTP_PROXY` when connecting to a local Kubernetes cluster, which may not work. To fix this, add `kube.teleport.cluster.local` to `NO_PROXY`. ## Ports @@ -263,4 +263,4 @@ traffic: You can only access enrolled applications and databases through the Teleport Proxy Service. The Teleport Application Service and Teleport Database Service use reverse tunnel -connections through the Teleport Proxy Service and cannot expose ports directly. \ No newline at end of file +connections through the Teleport Proxy Service and cannot expose ports directly.