From ff79e7fde794d8c001cfefaaeec4f03270e17504 Mon Sep 17 00:00:00 2001
From: kelseiv <47797004+kelseiv@users.noreply.github.com>
Date: Fri, 28 Aug 2020 11:08:27 -0700
Subject: [PATCH] Update bulk-ingest-cloud.md

---
 content/v2.0/write-data/bulk-ingest-cloud.md | 6 ++----
 1 file changed, 2 insertions(+), 4 deletions(-)

diff --git a/content/v2.0/write-data/bulk-ingest-cloud.md b/content/v2.0/write-data/bulk-ingest-cloud.md
index 0647dc25a..c53e9e00d 100644
--- a/content/v2.0/write-data/bulk-ingest-cloud.md
+++ b/content/v2.0/write-data/bulk-ingest-cloud.md
@@ -12,9 +12,7 @@ menu:
 products: [cloud]
 ---
 
-You might want to upload a large amount of previously existing *historical* data into InluxDB Cloud.
-Given our usage-based pricing and because the API is optimized for batched writing, the API is not recommended for ingesting bulk data.
-
-To migrate a large amount of existing historical data to Cloud, contact Support for assistance.
+To upload a large amount of previously existing *historical* data into InluxDB Cloud, contact Support for assistance.
 We’ll review your ingest rate limits, volume, and existing [data schema](/v2.0/reference/key-concepts/data-schema) to ensure the most efficient migration.
 
+Given our usage-based pricing and because the API is optimized for batched writing, we do not recommend using the API to ingest bulk data.