[DOCS-14070] Refresh Host Map screenshots and update terminology

content/en/infrastructure/hostmap.md

@@ -18,23 +18,23 @@ further_reading:
 
 Datadog's [Host Map][1] visualizes your hosts, pods, containers, and clusters, helping you to understand and diagnose your infrastructure.
 
-{{< img src="infrastructure/hostmap/new-host-map.png" alt="The Host Map showing hosts grouped by availability zone and colored by CPU usage. Hexagonal cells range from green (low usage) to orange-red (high usage). Groups include no availability-zone with 395 hosts, eastus with 183, eastus-1 with 153, and many additional regions." style="width:100%;" >}}
+{{< img src="infrastructure/hostmap/host-map-landing.png" alt="The Host Map showing hosts grouped by availability zone and colored by CPU usage. Hexagonal cells range from green (low usage) to orange-red (high usage). Groups include no availability-zone with 565 hosts, eastus with 192, eastus-1 with 147, northcentralus, and many additional regions." style="width:100%;" >}}
 
 ## Usage
 
-{{< img src="infrastructure/hostmap/query-selector.png" alt="The query selector dropdown showing a list of suggested queries such as 'What is the CPU usage across my hosts?' and 'How many errors are being logged across my infrastructure?', along with saved custom queries. A Create button and Filter views search field are at the top." style="width:60%;" >}}
+{{< img src="infrastructure/hostmap/query-list.png" alt="The query selector dropdown with suggested queries listed, including 'What is the CPU usage across my hosts?', 'How many errors are being logged across my infrastructure?', and 'Which services run on the busiest hosts, and are their pods ready?' A Create button, a Filter views search field, and a Show my queries toggle are at the top." style="width:60%;" >}}
 
 Use the drop-down in the upper left to view suggested queries, or the saved custom queries written by you or someone else in your organization. To write a custom query, click {{< ui >}}Create{{< /ui >}}.
 
-{{< img src="infrastructure/hostmap/draft-query.png" alt="The Draft Query editor with two levels. The parent object is set to Host with Fill by CPU usage. The child object is set to Pod with Fill by Readiness." style="width:100%;" >}}
+{{< img src="infrastructure/hostmap/draft-query-2.png" alt="The Draft query editor with two levels. The Main resource is set to Host with Fill by CPU usage. The Secondary resource is set to Pod with Fill by Readiness." style="width:100%;" >}}
 
-- {{< ui >}}Parent/Child Object{{< /ui >}}: Select resources ({{< ui >}}Host{{< /ui >}}, {{< ui >}}Pod{{< /ui >}}, {{< ui >}}Container{{< /ui >}}, {{< ui >}}Cluster{{< /ui >}}) to view. Parent and Child objects have hierarchical relationships.
+- {{< ui >}}Main/Secondary resource{{< /ui >}}: Select resources ({{< ui >}}Host{{< /ui >}}, {{< ui >}}Pod{{< /ui >}}, {{< ui >}}Container{{< /ui >}}, {{< ui >}}Cluster{{< /ui >}}) to view. Main and Secondary resources have hierarchical relationships.
 - {{< ui >}}Fill by{{< /ui >}}: By default, the color of each object represents CPU usage, where the color ranges from green (0% utilized) to orange (100% utilized). Use the {{< ui >}}Fill by{{< /ui >}} drop-down to color your objects by various metrics or signals, such as memory or error logs.
-- {{< ui >}}Size by{{< /ui >}}: If you do not specify a Child object, you can use the {{< ui >}}Size by{{< /ui >}} selector to size each object by a metric or signal.
+- {{< ui >}}Size by{{< /ui >}}: If you do not specify a Secondary resource, you can use the {{< ui >}}Size by{{< /ui >}} selector to size each object by a metric or signal.
   {{< img src="infrastructure/hostmap/size-by.png" alt="The Host Map query editor with Parent Object set to Host, Fill by set to CPU usage, and Size by set to Error logs. The map below shows 1.61k hosts as hexagons of varying sizes and colors, with a tooltip on one host showing 88% average CPU usage." style="width:85%;" >}}
 - {{< ui >}}Group by{{< /ui >}}: Spatially arrange your objects into groups. You can use multiple groupings. For example, if you group by `tags.availability-zone` `tags.instance-type`, your objects are first arranged by availability zone and then further subdivided by instance type.
 
-  {{< img src="infrastructure/hostmap/group-by.png" alt="The Host Map grouped by both tags.availability-zone and tags.instance-type. Hosts are arranged first into availability zone sections such as us-east-1a and us-east-1b, then subdivided by instance type such as m5a.2xlarge and t2.micro. Cells are colored by CPU usage from green to orange-red." style="width:85%;" >}}
+  {{< img src="infrastructure/hostmap/multiple-groupings.png" alt="The Host Map grouped by both tags.availability-zone and tags.instance-type. Hosts are arranged first into availability zone sections such as us-east-1a and us-east-1b, then subdivided by instance type such as m5a.2xlarge and m5d.6xlarge. Cells are colored by CPU usage from green to orange-red." style="width:85%;" >}}
 - {{< ui >}}Filter{{< /ui >}}: Limit the Host Map to a specific subset of your infrastructure. For example, you can filter by `production` to only view your production resources. The {{< ui >}}Filter{{< /ui >}} input supports logical operators (`AND`, `NOT`, `OR`) and wildcards (`*`). For example: `(tags.availability-zone:ap* OR tags.availability-zone:eu*) NOT tags.agent_version:5.3*`.
 
 ## Use cases