add hardware profile instances used

docs/en/observability/apm/troubleshooting/processing-performance.asciidoc

@@ -7,7 +7,10 @@ agent and server settings, versions, and protocol.
 
 We tested several scenarios to help you understand how to size the APM Server so that it can keep up with the load that your Elastic APM agents are sending:
 
-* Using the _CPU Optimized_ hardware template on AWS, GCP and Azure on {ecloud}, see link:https://www.elastic.co/guide/en/cloud/current/ec-configure-deployment-settings.html#ec-hardware-profiles[Hardware Profiles].
+* Using the _CPU Optimized_ hardware template on AWS, GCP and Azure on {ecloud} with the following instances, for more details see link:https://www.elastic.co/guide/en/cloud/current/ec-configure-deployment-settings.html#ec-hardware-profiles[Hardware Profiles]:
+    ** AWS: c6gd
+    ** Azure: fsv2
+    ** GCP: n2.68x32x45
 * For each hardware template, testing with several sizes: 1 GB, 4 GB, 8 GB, and 32 GB.
 * For each size, using a fixed number of APM agents: 10 agents for 1 GB, 30 agents for 4 GB, 60 agents for 8 GB, and 240 agents for 32 GB.
 * In all scenarios, using medium sized events. Events include