Merge pull request #296985 from MicrosoftDocs/repo_sync_working_branch

Confirm merge from repo_sync_working_branch to main to sync with https://github.com/MicrosoftDocs/azure-docs (branch main)

Author: Taojunshen

articles/azure-resource-manager/management/tag-support.md

@@ -2315,11 +2315,11 @@ To get the same data as a file of comma-separated values, download [tag-support.
 > | networkSecurityGroups / securityRules | No | No |
 > | networkSecurityPerimeters | Yes | Yes |
 > | networkVirtualAppliances | Yes | Yes |
-> | networkWatchers | Yes | Yes |
-> | networkWatchers / connectionMonitors | Yes | No |
-> | networkWatchers / flowLogs | Yes | No |
-> | networkWatchers / lenses | Yes | No |
-> | networkWatchers / pingMeshes | Yes | No |
+> | networkWatchers | No | No |
+> | networkWatchers / connectionMonitors | No | No |
+> | networkWatchers / flowLogs | No | No |
+> | networkWatchers / lenses | No | No |
+> | networkWatchers / pingMeshes | No | No |
 > | p2sVpnGateways | Yes | Yes |
 > | privateDnsZones | Yes | Yes |
 > | privateDnsZones / A | No | No |

articles/firewall/firewall-sftp.md

@@ -95,7 +95,7 @@ $natrulecollectiongroup.Properties.RuleCollection = $natrulecollection
 Set-AzFirewallPolicyRuleCollectionGroup -Name "rcg-01 " -FirewallPolicyObject $policy -Priority 200 -RuleCollection $natrulecollectiongroup.Properties.rulecollection
 
 ```
-## Deploy the firewall and configure the default route
+## Deploy the firewall
 
 ```azurepowershell
 

articles/network-watcher/network-watcher-agent-linux.md

@@ -84,7 +84,7 @@ Network Watcher Agent extension for Linux can be installed on the following Linu
 | Azure Linux | 2.0 |
 | CentOS <sup>1</sup> | 6.10 and 7 |
 | Debian | 7 and 8 |
-| OpenSUSE Leap | 42.3+ |
+| openSUSE Leap | 42.3+ |
 | Oracle Linux | 6.10 <sup>2</sup>, 7 and 8+ |
 | Red Hat Enterprise Linux (RHEL) | 6.10 <sup>3</sup>, 7, 8 and 9.2 |
 | Rocky Linux | 9.1 |

articles/storage/blobs/access-tiers-overview.md

@@ -44,7 +44,7 @@ To learn how to move a blob to the hot, cool, or cold tier, see [Set a blob's ac
 Data in the cool and cold tiers have slightly lower availability, but offer the same high durability, retrieval latency, and throughput characteristics as the hot tier. For data in the cool or cold tiers, slightly lower availability and higher access costs may be acceptable trade-offs for lower overall storage costs, as compared to the hot tier. For more information, see [SLA for storage](https://azure.microsoft.com/support/legal/sla/storage/v1_5/).
 
 Blobs are subject to an early deletion penalty if they are deleted, overwritten or moved to a different tier before the minimum number of days required by the tier have transpired. For example, a blob in the cool tier in a general-purpose v2 account is subject to an early deletion penalty if it's deleted or moved to a different tier before 30 days has elapsed. For a blob in the cold tier, the deletion penalty applies if it's deleted or moved to a different tier before 90 days has elapsed. This charge is prorated. For example, if a blob is moved to the cool tier and then deleted after 21 days, you'll be charged an early deletion fee equivalent to 9 (30 minus 21) days of storing that blob in the cool tier.
-Early deletion charges also occur if the entire object is rewritten through any operation (i.e. Put Blob, Put Block List, or Copy Blob) within the specified time window.
+Early deletion charges also occur if the entire object is rewritten through any operation (i.e. Put Blob, Put Block List, or Copy Blob) within the specified time window. This charge is prorated based on the data storage price of the corresponding tier, i.e. deleting an archived blob after 120 days will lead to this object being charged for 180 days. 
 
 > [!NOTE]
 > In an account that has soft delete enabled, a blob is considered deleted after it is deleted and retention period expires. Until that period expires, the blob is only  _soft-deleted_ and is not subject to the early deletion penalty.

articles/storage/common/storage-use-azcopy-v10.md

@@ -84,7 +84,7 @@ You can install AzCopy by using a Linux package that is hosted on the [Linux Sof
    ```
 
 
-### [zypper (OpenSUSE, SLES)](#tab/zypper)
+### [zypper (openSUSE, SLES)](#tab/zypper)
 
 1. Download the repository configuration package.