Changed Example 1 cmdlet to Update-AzWebAppAccessRestrictionConfig

[Cdoherty95]

Example 1 had Set-AzWebAppAccessRestriction as the cmdlet instead of Update-AzWebAppAccessRestrictionConfig.
Old Example 1:

PS C:\>Set-AzWebAppAccessRestriction -ResourceGroupName "Default-Web-WestUS" -Name "ContosoSite" -ScmSiteUseMainSiteRestrictionConfig

Corrected Example 1:

PS C:\>Update-AzWebAppAccessRestrictionConfig -ResourceGroupName "Default-Web-WestUS" -Name "ContosoSite" -ScmSiteUseMainSiteRestrictionConfig

Description

Checklist

• I have read the Submitting Changes section of CONTRIBUTING.md
• The title of the PR is clear and informative
• The appropriate ChangeLog.md file(s) has been updated:
  • For any service, the ChangeLog.md file can be found at src/{{SERVICE}}/{{SERVICE}}/ChangeLog.md
  • A snippet outlining the change(s) made in the PR should be written under the ## Upcoming Release header -- no new version header should be added
• The PR does not introduce breaking changes
• If applicable, the changes made in the PR have proper test coverage
• For public API changes to cmdlets:
  • a cmdlet design review was approved for the changes in this repository (Microsoft internal only)
  • the markdown help files have been regenerated using the commands listed here

[adxsdkps]

Can one of the admins verify this patch?

[msftclas]

All CLA requirements met.

[msJinLei]

/azp run

[azure-pipelines]

Azure Pipelines successfully started running 3 pipeline(s).

[msJinLei]

@Cdoherty95 Please sign the CLA.

[Cdoherty95]

@msJinLei My apologies on the delay in signing the CLA

[isra-fel]

Thanks for your contribution! Looking good for me.