From bf8f5e932eb5013a9353003828c89332bcdf2882 Mon Sep 17 00:00:00 2001
From: Mike Thomas <78363703+mike-j-thomas@users.noreply.github.com>
Date: Sat, 4 Sep 2021 04:50:12 +0900
Subject: [PATCH] Update pricing.ejs (#1910)

Another grammar fix. I think that because we state "wherever it is deployed," we should follow with "anywhere," rather than "anything."
---
 website/views/pages/pricing.ejs | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)

diff --git a/website/views/pages/pricing.ejs b/website/views/pages/pricing.ejs
index 002b326fb1..e465f483ae 100644
--- a/website/views/pages/pricing.ejs
+++ b/website/views/pages/pricing.ejs
@@ -1199,7 +1199,7 @@
                 <span style="color: #6A67FE; right: 0; top: 24px;" class="position-absolute fa fa-angle-down"></span>
               </p>
               <p id="faq__answer10" class="collapse" aria-labelledby="faq__question10">
-                Since Fleet is self-managed, some metadata is stored wherever it is deployed (e.g. Amazon, Azure, Google, your own data center, hybrid cloud, anything).  That's done using a MySQL database, but the bulk of the data is not stored there — instead, it flows directly into a tool like Splunk or ElasticSearch. You can send that information to any of Fleet's supported log destinations.
+                Since Fleet is self-managed, some metadata is stored wherever it is deployed (e.g. Amazon, Azure, Google, your own data center, hybrid cloud, anywhere).  That's done using a MySQL database, but the bulk of the data is not stored there — instead, it flows directly into a tool like Splunk or ElasticSearch. You can send that information to any of Fleet's supported log destinations.
               </p>
             </div>
           </div>