Solved comments

Author: yaakoviyun

src/ResourceManager/Sql/Commands.Sql/ChangeLog.md

@@ -18,7 +18,7 @@
         - Additional information about change #1
 -->
 ## Current Release
-* Fixed issue where using Update-AzureRmSqlDatabaseVulnerabilityAssessmentSettings with storage account name parameter set
+* Fixed issue with using Update-AzureRmSqlDatabaseVulnerabilityAssessmentSettings with storage account name parameter set
 
 ## Version 4.11.5
 * Fixed issue where some backup cmdlets would not recognize the current azure subscription

src/ResourceManager/Sql/Commands.Sql/VulnerabilityAssessment/Cmdlet/VulnerabilityAssessmentSettings/UpdateAzureSqlDatabaseVulnerabilityAssessmentSettings.cs

@@ -237,7 +237,7 @@ protected override DatabaseVulnerabilityAssessmentSettingsModel PersistChanges(D
             }
             else 
             {
-				return ModelAdapter.SetDatabaseVulnerabilityAssessmentSettingsWithStorageAccesKey(model);
+				return ModelAdapter.SetDatabaseVulnerabilityAssessmentSettingsWithStorageAccessKey(model);
             }
         }
 

src/ResourceManager/Sql/Commands.Sql/VulnerabilityAssessment/Services/SqlVulnerabilityAssessmentAdapter.cs

@@ -77,7 +77,7 @@ public DatabaseVulnerabilityAssessmentSettingsModel SetDatabaseVulnerabilityAsse
 		/// <summary>
         /// Set settings with storage access key
         /// </summary>
-        public DatabaseVulnerabilityAssessmentSettingsModel SetDatabaseVulnerabilityAssessmentSettingsWithStorageAccesKey(DatabaseVulnerabilityAssessmentSettingsModel model)
+        public DatabaseVulnerabilityAssessmentSettingsModel SetDatabaseVulnerabilityAssessmentSettingsWithStorageAccessKey(DatabaseVulnerabilityAssessmentSettingsModel model)
         {
             var resourceGroupName = AzureCommunicator.GetStorageResourceGroup(model.StorageAccountName);
             var storageContainerInfo = VulnerabilityAssessmentCommunicator.GetStorageContainerInfo(resourceGroupName, model.StorageAccountName,