Update pricing.ejs (#1909)

Fixed a grammatical error in the FAQs
2021-09-02 21:05:12 +09:00
parent b862c6d577
commit 4343182323
1 changed files with 1 additions and 1 deletions
@@ -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, their 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, 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.
              </p>
            </div>
          </div>