Polish changelog for upcoming release (Azure#14559)

* Polish for upcoming release

* update changelog

* Revert couple changes

* Update file

Author: dingmeng-xue

src/IotHub/IotHub/ChangeLog.md

@@ -18,7 +18,7 @@
         - Additional information about change #1
 -->
 ## Upcoming Release
-* Updates IoT Hub Management SDK and models to version 3.0.0 (api-version 2020-03-01)
+* Updated IoT Hub Management SDK and models to version 3.0.0 (api-version 2020-03-01)
 
 ## Version 2.7.2
 * Fixed a regression regarding SAS token generation

src/RedisEnterpriseCache/Az.RedisEnterpriseCache.psd1

@@ -12,7 +12,7 @@
 RootModule = './Az.RedisEnterpriseCache.psm1'
 
 # Version number of this module.
-ModuleVersion = '1.0.0'
+ModuleVersion = '0.1.0'
 
 # Supported PSEditions
 CompatiblePSEditions = 'Core', 'Desktop'

src/ServiceFabric/ServiceFabric/ChangeLog.md

@@ -18,28 +18,15 @@
         - Additional information about change #1
 -->
 ## Upcoming Release
-* Add parameters to `Add-AzServiceFabricNodeType` to facilitate easy alternate OS image creation for new node type.
-    Parameters: `VMImagePublisher`, `VMImageOffer`, `VMImageSku`, `VMImageVersion`
-    - Example usage: For a Ubuntu 16.04 cluster, add a new Ubuntu 18 node type: <br/>
-    ```powershell
-    $resouceGroup="Group1"
-    $clusterName="Contoso01SFCluster"
-    $nodeTypeName="nt2"
-    $securePassword = ConvertTo-SecureString -String 'Password$123456' -AsPlainText -Force
-
-    Add-AzServiceFabricNodeType -ResourceGroupName $resouceGroup  -ClusterName $clusterName -NodeType $nodeTypeName -Capacity 5 -VmUserName adminuser -VmPassword $securePassword -DurabilityLevel Silver -Verbose -VMImageSku 18.04-LTS
-    ```
-* Add parameter `IsPrimaryNodeType` to `Add-AzServiceFabricNodeType` to be able to create an additional primary node type,
-    for the purpose of transitioning the primary node type to another one in the case of OS migration.
+* Added parameters `VMImagePublisher`, `VMImageOffer`, `VMImageSku`, `VMImageVersion` to `Add-AzServiceFabricNodeType` to facilitate easy alternate OS image creation for new node type.
+* Added parameter `IsPrimaryNodeType` to `Add-AzServiceFabricNodeType` to be able to create an additional primary node type, for the purpose of transitioning the primary node type to another one in the case of OS migration.
 * `Add-AzServiceFabricNodeType` now correctly copies the LinuxDiagnostic extension. This was previously not working for Linux.
 * `Add-AzServiceFabricNodeType` now correctly copies the RDP/SSH load balancer inbound NAT port mapping to the new node type.
-* Add template for `UbuntuServer1804` for creating Ubuntu 18.04 clusters using `New-AzServiceFabricCluster`.
-* `Remove-AzServiceFabricNodeType` was incorrectly blocking Bronze durability node types for removal, and this has been updated
-    to only block when the Bronze durability level differs between the SF node type and VMSS setting.
+* Added template for `UbuntuServer1804` for creating Ubuntu 18.04 clusters using `New-AzServiceFabricCluster`.
+* `Remove-AzServiceFabricNodeType` was incorrectly blocking Bronze durability node types for removal, and this has been updated to only block when the Bronze durability level differs between the SF node type and VMSS setting.
 * Added cmdlet `Update-AzServiceFabricVmImage` to update the delivered SF runtime package type. This must be changed when migrating from Ubuntu 16 to 18.
 * Added cmdlet `Update-AzServiceFabricNodeType` to update the properties of a cluster node type. For now this is solely used to update whether the node type is primary via bool parameter `-IsPrimaryNodeType $false`.
-* `Update-AzServiceFabricReliability` is now able to update reliability level when the cluster has more than one primary node type.
-    To do this, the name of the node type is supplied via the new -NodeType parameter.
+* `Update-AzServiceFabricReliability` is now able to update reliability level when the cluster has more than one primary node type. To do this, the name of the node type is supplied via the new -NodeType parameter.
 
 ## Version 2.2.2
 * Fixed `Add-AzServiceFabricNodeType`. Added node type to service fabric cluster before creating virtual machine scale set.

src/Websites/Websites/ChangeLog.md

@@ -18,7 +18,7 @@
         - Additional information about change #1
 -->
 ## Upcoming Release
-* Add-AzWebAppAccessRestrictionRule: Allow all supported Service Tags and validate against Service Tag API.
+* Updated `Add-AzWebAppAccessRestrictionRule` to allow all supported Service Tags and validate against Service Tag API.
 
 ## Version 2.4.0
 * Introduced an option to give custom timeout for `Publish-AzWebApp` 

tools/Az/Az.psd1

@@ -103,7 +103,7 @@ RequiredModules = @(@{ModuleName = 'Az.Accounts'; ModuleVersion = '2.2.6'; },
                @{ModuleName = 'Az.PrivateDns'; RequiredVersion = '1.0.3'; }, 
                @{ModuleName = 'Az.RecoveryServices'; RequiredVersion = '3.4.1'; }, 
                @{ModuleName = 'Az.RedisCache'; RequiredVersion = '1.4.0'; }, 
-               @{ModuleName = 'Az.RedisEnterpriseCache'; RequiredVersion = '1.0.0'; }, 
+               @{ModuleName = 'Az.RedisEnterpriseCache'; RequiredVersion = '0.1.0'; }, 
                @{ModuleName = 'Az.Relay'; RequiredVersion = '1.0.3'; }, 
                @{ModuleName = 'Az.Resources'; RequiredVersion = '3.3.0'; }, 
                @{ModuleName = 'Az.ServiceBus'; RequiredVersion = '1.4.1'; }, 

tools/VersionController/MinimalVersion.csv

@@ -1,3 +1,2 @@
 "Module","Minimal Version"
-"Az.Databricks","1.1.0"
 "Az.RedisEnterpriseCache","1.0.0"