Skip to content

Commit e3b1e68

Browse files
committed
PR Clarity feedback
1 parent bfe0702 commit e3b1e68

1 file changed

Lines changed: 6 additions & 6 deletions

File tree

articles/energy-data-services/how-to-manage-upgrade-settings.md

Lines changed: 6 additions & 6 deletions
Original file line numberDiff line numberDiff line change
@@ -24,10 +24,10 @@ Azure Data Manager for Energy provides two upgrade policy options:
2424

2525
| Policy | Description |
2626
|--------|-------------|
27-
| **Automatic** | Your instance is automatically upgraded when a new milestone release is available. This is the default setting for all instances. |
27+
| **Automatic** | Your instance is automatically upgraded when a new milestone release is available. This option is the default setting for all instances. |
2828
| **Deferred** | Your instance upgrade is deferred, giving you up to 30 days to validate the new milestone release before your instance is upgraded. |
2929

30-
If you have multiple Azure Data Manager for Energy instances, you can set different upgrade policies for each one. For example, you might set one instance to **Automatic** so it upgrades immediately when a new milestone is released, allowing you to test and validate the changes. Meanwhile, you can set your production instance to **Deferred** to delay the upgrade until you've completed your testing. At any point during the 30-day window, you can mark your deferred instance as ready for upgrade. If you don't take action, the instance is automatically upgraded at the end of the 30-day window.
30+
If you have multiple Azure Data Manager for Energy instances, you can set different upgrade policies for each one. For example, you might set one instance to **Automatic** so it upgrades immediately when a new milestone is released, allowing you to test and validate the changes. Meanwhile, you can set your production instance to **Deferred** to delay the upgrade until you complete your testing. At any point during the 30-day window, you can mark your deferred instance as ready for upgrade. If you don't take action, the instance is automatically upgraded at the end of the 30-day window.
3131

3232
## View upgrade settings
3333

@@ -40,7 +40,7 @@ If you have multiple Azure Data Manager for Energy instances, you can set differ
4040
1. On the **Upgrade Settings** page, you can view:
4141
- **Current milestone version**: The current milestone version your instance is running (for example, M25 or M26).
4242
- **Upgrade policy**: Whether your instance is set to **Automatic** or **Deferred** upgrades.
43-
- **Auto upgrade after date**: If your upgrade policy is set to **Deferred** and a milestone upgrade is available, this field shows the date when your instance will be automatically upgraded.
43+
- **Auto upgrade after date**: If your upgrade policy is set to **Deferred** and a milestone upgrade is available, this field shows the date when your instance is automatically upgraded.
4444

4545
ADD SCREENSHOT HERE
4646

@@ -99,7 +99,7 @@ If your upgrade policy is set to **Deferred** and a milestone upgrade is availab
9999

100100
When a new milestone release is available and your upgrade policy is set to **Deferred**:
101101

102-
1. After all instances with the **Automatic** upgrade policy have been upgraded, the Azure Data Manager for Energy team sets the **30-Day Window End Date**, which is approximately 30 days from that point.
102+
1. After all instances with the **Automatic** upgrade policy are upgraded, the Azure Data Manager for Energy team sets the **30-Day Window End Date**, which is approximately 30 days from that point.
103103

104104
1. The **30-Day Window End Date** is displayed on the **Upgrade Settings** page in the Azure portal.
105105

@@ -114,11 +114,11 @@ When a new milestone release is available and your upgrade policy is set to **De
114114

115115
### What happens if I find an issue with Azure Data Manager for Energy during the 30-day window?
116116

117-
If you discover an issue during the 30-day window, contact Azure support. Depending on the severity of the issue, the Azure Data Manager for Energy team may deploy a hotfix. If a hotfix is required, the 30-day timer is paused when the issue is identified and resumes once the hotfix has been deployed.
117+
If you discover an issue during the 30-day window, contact Azure support. Depending on the severity of the issue, the Azure Data Manager for Energy team may deploy a hotfix. If a hotfix is required, the 30-day timer is paused when the issue is identified and resumes once the hotfix is deployed.
118118

119119
## Next steps
120120

121-
Learn more about what's included in each milestone release and Azure Data Manager for Energy:
121+
Learn more about each milestone release and Azure Data Manager for Energy:
122122

123123
> [!div class="nextstepaction"]
124124
> [Release notes](release-notes.md)

0 commit comments

Comments
 (0)