From f1f68273bdd2919755f4c7d8d61c55b410fcb354 Mon Sep 17 00:00:00 2001
From: Tony Gauda <5620541+tgauda@users.noreply.github.com>
Date: Fri, 28 Jan 2022 10:18:15 -0500
Subject: [PATCH] Discuss API endpoints that should be public

---
 docs/01-Using-Fleet/FAQ.md | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)

diff --git a/docs/01-Using-Fleet/FAQ.md b/docs/01-Using-Fleet/FAQ.md
index 33e9d62ed3..486b87a650 100644
--- a/docs/01-Using-Fleet/FAQ.md
+++ b/docs/01-Using-Fleet/FAQ.md
@@ -187,6 +187,6 @@ Yes, Orbit can be run alongside osquery. The osquery instance that Orbit runs us
 
 If Fleet can't send logs to the destination, it will return an error to osquery. This causes osquery to retry sending the logs. The logs will then be stored in osquery's internal buffer until they are sent successfully, or they get expired if the `buffered_log_max`(defaults to 1,000,000 logs) is exceeded. Check out the [Remote logging buffering section](https://osquery.readthedocs.io/en/latest/deployment/remote/#remote-logging-buffering) on the osquery docs for more on this behavior.
 
-##What API endpoints should I expose to the public internet?
+## What API endpoints should I expose to the public internet?
 
 If you would like to manage hosts that can travel outside your VPN or intranet we recommend only exposing the "/api/v1/osquery" endpoint to the public internet.