RDoc-3591 Cloud: Portal -> Products Tab -> View the Cluster Health - add the product history widget & RDoc-3592 Cloud: Maintenance & Troubleshooting -> add a section about the product history widget & RDoc-3593 Cloud: Scaling -> add info about the email notifications (product scale up/down)

cloud/cloud-maintenance-troubleshooting.mdx

@@ -42,15 +42,16 @@ status.
 ## Cluster Health
 
 **Cluster Health** helps keep your cluster healthy by providing suggestions and incidents history.  
-This dashboard has three separated sections:
+This dashboard has four separated sections:
 
-- [Cluster Nodes Availability](cloud-maintenance-troubleshooting#cluster-nodes-availability)
+- [Nodes Availability](cloud-maintenance-troubleshooting#nodes-availability)
 - [Incidents History](cloud-maintenance-troubleshooting#incidents-history)
 - [Suggestions](cloud-maintenance-troubleshooting#suggestions)
+- [Product changes in time](cloud-maintenance-troubleshooting#product-changes-in-time)
 
-## Cluster Nodes Availability
+## Nodes Availability
 
-The **Cluster Nodes Availability** section shows the availability status of each node within your cluster.
+The **Nodes Availability** section shows the availability status of each node within your cluster.
 It provides a real-time, visual overview of how reliably each node has been operating in the current month.
 
 Each node is represented by a gauge showing its availability percentage, helping you quickly assess the overall health of your system.
@@ -66,6 +67,8 @@ Each node's status is color-coded based on its availability percentage:
 | 95% – 99.9%  | Degraded | 🟡 Yellow |
 | < 95%        | Critical | 🔴 Red    |
 
+!["Cluster Health: Nodes availability section"](./assets/cluster-health-nodes-availability.png)
+
 These thresholds help you identify which nodes might require attention:
 
 - **Healthy** nodes have consistently high uptime and are performing reliably.
@@ -91,6 +94,7 @@ Incidents are split into *six* categories. **Description** column contains addit
 | Disk          | Product's available disk space is low.                                                 |
 | IO            | Product is experiencing high input/output operations.                                  |
 | Availability  | Product is currently not responding to input or commands or has been restarted.        |
+
 ## Suggestions
 
 This section displays suggestions for a selected *cluster node* based on incident trends.
@@ -132,5 +136,10 @@ Below examples of the suggestions with the analyses:
 
 !["Cluster Health: An example of `Current period above threshold by percents` analyse"](./assets/cluster-health-suggestions-current-month-above-threshold-by-percents.png)
 
+## Product changes in time
+
+This view shows changes in product type over time. Changes can be presented as a graph or a table.
 
+!["Cluster Health: Product changes in time - graph"](./assets/cluster-health-product-changes-in-time-graph.png)  
 
+!["Cluster Health: Product changes in time - table"](./assets/cluster-health-product-changes-in-time-table.png)

cloud/cloud-scaling.mdx

@@ -38,7 +38,7 @@ two RavenDB instances using:
 To scale a RavenDB Cloud instance, open your [portal](../cloud/portal/cloud-portal.mdx)'s [Products tab](../cloud/portal/cloud-portal-products-tab.mdx) 
 and click the **Manage** button for the product you want to change.
 
-![Figure 1 - Manage product](./assets/portal-product-list-manage-button.png)
+![Manage product](./assets/portal-product-list-manage-button.png)
 
 In the main section, you can find controls to **Change Instance Type** or **Change Storage**.  
 
@@ -48,7 +48,7 @@ The scaling buttons are presented only for [Development](../cloud/cloud-instance
 The [Free](../cloud/cloud-instances.mdx#a-free-cloud-node) product doesn't show them because its Tier includes only one configuration.  
 </Admonition>
 
-![Figure 2 - Scaling buttons](./assets/portal-product-edit-storage-and-instance-type-area.png)
+![Scaling buttons](./assets/portal-product-edit-storage-and-instance-type-area.png)
 
 **1.** Click [Change Instance Type](../cloud/cloud-scaling.mdx#scaling---change-instance-type) to reconfigure your product.  
 **2.** Click [Change Storage](../cloud/cloud-scaling.mdx#scaling---change-storage) to modify your product's storage parameters.  
@@ -63,7 +63,7 @@ because it is a multi-node cluster and the nodes are updated in a **rolling upda
 <Admonition type="warning" title="">
 Instances have *IO limits* (**IOPS** and **Throughput**) and it may impact the Disk performance.
 
-![Figure 3 - Instance & Disk limitations](./assets/portal-product-details-instance-limitations-disk-limitations.png)
+![Instance & Disk limitations](./assets/portal-product-details-instance-limitations-disk-limitations.png)
 
 In the figure above, the **Disk Throughput** parameter is lower than the **Instance Throughput**.
 To avoid IO throttling by the instance type, make sure to use an instance type able to fully utilize your disk capabilities.
@@ -79,19 +79,22 @@ that would allow your product to properly handle its expected workload.
 Scaling product to P60 or P70 can be done only via support request.
 </Admonition>
 
-![Figure 4 - Scaling instance type](./assets/portal-product-details-edit-tier.png)
+![Scaling instance type](./assets/portal-product-details-edit-tier.png)
 
 You can upscale or downscale only within the current Product Tier. The *Development* Tier **Dev30** configuration,
 for example, can upscale to **Dev50**, but not to the Production Tier **PB10** configuration.  
 Your databases and data will be automatically migrated into your new configuration.
 
+![Scaling storage](./assets/scaleupdown-email-notification.png)
+
+Once you upscale or downscale, you will receive an email notification of this operation.
 
 ## Scaling - Change Storage 
 
 There are two types of storage: **Standard** and **Premium**. They differ significantly in capabilities and customization options 
 depending on the cloud provider in question. Pick either to change your current storage capacity.  
 
-![Figure 5 - Scaling storage](./assets/portal-product-details-edit-storage.png)
+![Scaling storage](./assets/portal-product-details-edit-storage.png)
 ### AWS Disks
 
 #### AWS Standard & Premium - Default Performance
@@ -104,7 +107,7 @@ For **Premium** Disks, the **IOPS** parameter is set to **500** by default. The
 
 The **Premium** Disk type on **AWS** lets you choose the number of **IOPS** (Input/Output Operations Per Second) that the instance can handle.
 
-![Figure 6 - Customized IOPS on AWS Premium Disks](./assets/portal-product-details-edit-storage-with-iops.png)
+![Customized IOPS on AWS Premium Disks](./assets/portal-product-details-edit-storage-with-iops.png)
 
 <Admonition type="info" title="">
 The cost per IOPS is dependent on the selected region.
@@ -126,7 +129,7 @@ level of performance, the **Premium** Disk type on **Azure** lets you use a high
 long as you need it. This feature allows you to increase the disk performance without increasing the disk size. 
 You can then return to the original Tier when you no longer need the additional performance. 
 
-![Figure 7 - Azure Performance Tier on Azure Premium Disks](./assets/portal-product-details-edit-storage-with-azure-performance-tier.png)
+![Azure Performance Tier on Azure Premium Disks](./assets/portal-product-details-edit-storage-with-azure-performance-tier.png)
 
 <Admonition type="info" title="">
 The cost of running on a higher *Performance Tier* is the same as
@@ -152,7 +155,7 @@ The use of a data disk is mandatory for deployments requiring more than 1TB of s
 ## Additional product nodes - General
 The *Production Tier* products can be expanded by adding *additional nodes* to the cluster.
 
-![Figure 8 - Cluster view with additional product nodes](./assets/studio-cluster-view-with-additional-nodes.png)
+![Cluster view with additional product nodes](./assets/studio-cluster-view-with-additional-nodes.png)
 
 <Admonition type="info" title="">
 This option **is not available** for **PS** instance types.  
@@ -169,7 +172,7 @@ The process of adding a new node **does not guarantee** that the node will be di
 The new product node **does not belong to any database group**. The User should do this *manually* by adding the new node to the database group.  
 This operation is described [here](https://ravendb.net/docs/article-page/latest/csharp/studio/database/settings/manage-database-group#database-group-topology---add-new-node).
 
-![Figure 9 - Add a new node to the database group](./assets/studio-add-new-node-to-database-group.png)
+![Add a new node to the database group](./assets/studio-add-new-node-to-database-group.png)
 
 
 

cloud/portal/cloud-portal-products-tab.mdx

@@ -122,7 +122,8 @@ It's useful for analysing usage, instance overload and traffic.
 !["Figure 10 - Cluster Health: General View"](./assets/portal-product-details-cluster-health.png)
 
 This allows you to analyse your cluster incidents for a selected *time period*, *cluster node*, *severity*, *category* and *event status*.  
-In addition, **Cluster Health** generates suggestions for a selected *cluster node* based on incident trends that can help resolve cluster stability issues.  
+In addition, **Cluster Health** generates suggestions for a selected *cluster node* based on incident trends that can help resolve cluster stability issues.
+The view also shows node availability for the last 30 days and a history of product type changes.  
 It's useful for analysing usage, instance overload and traffic.  
 
 More details can be found [here](../cloud-maintenance-troubleshooting.mdx#cluster-health).