Remove potentially misleading part of automated reporting docs (#29297)

website/content/docs/enterprise/license/utilization-reporting.mdx

@@ -10,12 +10,7 @@ description: >-
 @include 'alerts/enterprise-only.mdx'
 
 Automated license utilization reporting sends license utilization data to
-HashiCorp without requiring you to manually collect and report them. It also
-lets you review your license usage with the monitoring solution you already use
-(for example Splunk, Datadog, or others) so you can optimize and manage your
-deployments. Use these reports to understand how much more you can deploy under
-your current contract, protect against overutilization, and budget for predicted
-consumption.
+HashiCorp without requiring you to manually collect and report them.
 
 Automated reporting shares the minimum data required to validate license
 utilization as defined in our contracts. They consist of mostly computed metrics
@@ -228,20 +223,20 @@ HashiCorp collects the following utilization data as JSON payloads:
          - `nonentity` - The sum of tokens without an entity attached
 - `metadata` - Optional product-specific metadata
    - `billing_start` - The billing start date associated with the reporting cluster (license start date if not configured).
-   
+
    <Note title="Important change to supported versions">
-      
-      As of 1.16.7, 1.17.3 and later, 
-      the <a href="/vault/docs/concepts/billing-start-date">billing start date</a> automatically 
+
+      As of 1.16.7, 1.17.3 and later,
+      the <a href="/vault/docs/concepts/billing-start-date">billing start date</a> automatically
       rolls over to the latest billing year at the end of the last cycle.
-        
+
       For more information, refer to the upgrade guide for your Vault version:
 
       [Vault v1.16.x](/vault/docs/upgrading/upgrade-to-1.16.x#auto-rolled-billing-start-date),
       [Vault v1.17.x](/vault/docs/upgrading/upgrade-to-1.17.x#auto-rolled-billing-start-date)
 
-    </Note> 
-    
+    </Note>
+
    - `cluster_id` - The cluster UUID as shown by `vault status` on the reporting
      cluster