From 0ca244ee185863978c005821b89e0a796c8ba0cc Mon Sep 17 00:00:00 2001 From: Taylor Wakefield Date: Tue, 25 Feb 2020 15:32:04 -0800 Subject: [PATCH] Update faq.md (#3382) fixed grammar for new FAQ on scalability / hardware recommendations --- docs/4.2/faq.md | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) diff --git a/docs/4.2/faq.md b/docs/4.2/faq.md index 82f1dca24ec..006e196167a 100644 --- a/docs/4.2/faq.md +++ b/docs/4.2/faq.md @@ -35,7 +35,7 @@ it has been fixed with Teleport 4.0. Once you've upgraded your Teleport Cluste option `--auth-server` to point to web proxy address (this would be `public_addr` and `web_listen_addr` in file configuration). As defined in [Adding a node located behind NAT - Teleport Node Tunneling](admin-guide.md#adding-a-node-located-behind-nat) -### What's Teleport scalability and hardware recommendations? +### What are Teleport's scalability and hardware recommendations? We recommend setting up Teleport with a [High Availability configuration](admin-guide.md#high-availability). Below is our recommended hardware for the Proxy and Auth server. If you plan to connect more than 10,000 nodes, please @@ -98,4 +98,4 @@ This allows Teleport Pro to print a warning if users are exceeding the usage lim of their license. The reporting library code is [on Github](https://github.com/gravitational/reporting). Reach out to `sales@gravitational.com` if you have questions about the commercial -edition of Teleport. \ No newline at end of file +edition of Teleport.