vcenterreceiver updates changelog to be more concise & clear

Author: StefanKurek

.chloggen/vcenter-receiver_remove_extra_host_perf_metrics.yaml

@@ -7,7 +7,7 @@ change_type: breaking
 component: vcenterreceiver
 
 # A brief description of the change.  Surround your text with quotes ("") if it needs to start with a backtick (`).
-note: "Removes the ability to sent 5 historical metrics per collection for Host Resource performance metrics."
+note: Several host performance metrics now return 1 data point per time series instead of 5.
 
 # Mandatory: One or more tracking issues related to the change. You can use the PR number here if no issue exists.
 issues: [34708]
@@ -16,11 +16,12 @@ issues: [34708]
 # These lines will be padded with 2 spaces and then inserted directly into the document.
 # Use pipe (|) for multiline entries.
 subtext: |
-Sending 5 historical metrics already did not match up with what was being done with the VM performance metrics.
-It could easily lead to situations where timetamps were the tail end of these 5 datapoints would end up being
-picked up by the following collection as well. This change also fixes an issue with the googlecloud exporter
-seeing these datapoints (20s apart) as duplicates. Following is the list of affected metrics which will now only
-report a single datapoint per set of unique attribute values.
+The 5 data points previously sent represented consecutive 20s sampling periods. Depending on the collection interval 
+these could easily overlap. Sending just the latest of these data points is more in line with other performance metrics.
+
+This change also fixes an issue with the googlecloud exporter seeing these datapoints as duplicates.
+
+Following is the list of affected metrics which will now only report a single datapoint per set of unique attribute values.
 - vcenter.host.cpu.reserved
 - vcenter.host.disk.latency.avg
 - vcenter.host.disk.latency.max