Update Add-AzureRmLogProfile.md with @vcanaa comments

Fixed with comments from @vcanaa 
a) Removed the limit of one profile and one storage account from verbatim. This allows the verbatim to be applicable even when the limits are increased.
b) Retaining "Global","West US" format to align with the format returned by  Get-AzureLocation | Select DisplayName 
c) Modified -Location "Global,West US" to -Location "Global","West US"
d) Fixed typo for ever to forever

Author: angshumannayak

src/ResourceManager/Insights/Commands.Insights/help/Add-AzureRmLogProfile.md

@@ -8,7 +8,7 @@ schema: 2.0.0
 # Add-AzureRmLogProfile
 
 ## SYNOPSIS
-Creates a new activity log profile, there can be only one log profile per subscription. This profile is used to either archive the activity log to a storage account or stream it to an Azure event hub. Only a single standard storage account (premium storage account is not supported) per subscription is supported. It could either be of type ARM or Classic. If it's logged to a storage account, the cost of storing the activity log is billed at normal standard storage rates. 
+Creates a new activity log profile. This profile is used to either archive the activity log to a storage account or stream it to an Azure event hub. Only standard storage account (premium storage account is not supported) is supported. It could either be of type ARM or Classic. If it's logged to a storage account, the cost of storing the activity log is billed at normal standard storage rates. 
 
 In the activity log, events can pertain to a region or could be "Global". Global essentially means these events are region agnostics and are independent of region, in fact majority of events fall into this category. If the activity log profile is set from the portal, it implicitly adds "Global" along with any other region selected in the user interface. When using the cmdlet, the location as "Global" must be explicitly mentioned apart from any other region.  
 
@@ -26,7 +26,7 @@ The **Add-AzureRmLogProfile** cmdlet creates a log profile.
 ## EXAMPLES
 ### Example 1 : Add a new log profile to export the activity log matching the location condition to a storage account 
 ```yaml
-Add-AzureRmLogProfile -Locations "Global,West US" -Name ExportLogProfile -StorageAccountId /subscriptions/40gpe80s-9sb7-4f07-9042-b1b6a92ja9fk/resourceGroups/activitylogRG/providers/Microsoft.Storage/storageAccounts/activitylogstorageaccount 
+Add-AzureRmLogProfile -Locations "Global","West US" -Name ExportLogProfile -StorageAccountId /subscriptions/40gpe80s-9sb7-4f07-9042-b1b6a92ja9fk/resourceGroups/activitylogRG/providers/Microsoft.Storage/storageAccounts/activitylogstorageaccount 
 ```
 
 ## PARAMETERS
@@ -48,7 +48,7 @@ Accept wildcard characters: False
 
 ### -Locations
 Specifies the location of the log profile.
-Valid values: Run below cmdlet   to get the latest list of locations. 
+Valid values: Run below cmdlet to get the latest list of locations. 
 ```yaml
 Get-AzureLocation | Select DisplayName
 ```
@@ -81,7 +81,7 @@ Accept wildcard characters: False
 ```
 
 ### -RetentionInDays
-Specifies the retention policy, in days. This is the number of days the logs are preserved in the storage account specified. To retain the data forever set this 0. If it's not specified, then it defaults to 0 which is retain for ever.
+Specifies the retention policy, in days. This is the number of days the logs are preserved in the storage account specified. To retain the data forever set this 0. If it's not specified, then it defaults to 0 which means retain forever.
 
 ```yaml
 Type: Int32