From 18f61c1def03552e2fa3e9197b789afbff113d02 Mon Sep 17 00:00:00 2001
From: kelseiv <47797004+kelseiv@users.noreply.github.com>
Date: Tue, 7 May 2019 10:15:52 -0700
Subject: [PATCH] Update rate-limits.md

---
 content/v2.0/cloud/rate-limits.md | 17 -----------------
 1 file changed, 17 deletions(-)

diff --git a/content/v2.0/cloud/rate-limits.md b/content/v2.0/cloud/rate-limits.md
index 8a7c374a9..1c8fc2750 100644
--- a/content/v2.0/cloud/rate-limits.md
+++ b/content/v2.0/cloud/rate-limits.md
@@ -28,20 +28,3 @@ When a request exceeds the rate limit for the endpoint, the InfluxDB API returns
 
 - HTTP 429 “Too Many Requests”
 - Retry-After: xxx (seconds to wait before retrying the request)
-
-<!-- potential information to add moving forward?
-
-Use HTTP headers to review the following:
-
-?: the rate limit ceiling for a given endpoint
-?: the number of requests remaining in the 4 hour window (will we provide functionality to change this window?)
-?: time remaining before the rate limit resets, in <precision> seconds
-
-## Rate limit messaging
-
-When a request exceeds the rate limit for a given API endpoint, the API returns the following errors in the response body:
-
-{ "errors": [ { "code": ??, "message": "??" } ] }
-
--->
-