Update Certificate Type description

[jlichwa]

Latest improvements:

MSFT employees can try out our new experience at OpenAPI Hub - one location for using our validation tools and finding your workflow.

Contribution checklist:

• I have reviewed the documentation for the workflow.
• Validation tools were run on swagger spec(s) and have all been fixed in this PR.
• The OpenAPI Hub was used for checking validation status and next steps.

ARM API Review Checklist

• Service team MUST add the "WaitForARMFeedback" label if the management plane API changes fall into one of the below categories.
• adding/removing APIs.
• adding/removing properties.
• adding/removing API-version.
• adding a new service in Azure.

Failure to comply may result in delays for manifest application. Note this does not apply to data plane APIs.

• If you are blocked on ARM review and want to get the PR merged urgently, please get the ARM oncall for reviews (RP Manifest Approvers team under Azure Resource Manager service) from IcM and reach out to them.
  Please follow the link to find more details on API review process.

[AutorestCI]

Automation for azure-sdk-for-python

Nothing to generate for azure-sdk-for-python

[AutorestCI]

Automation for azure-sdk-for-go

The initial PR has been merged into your service PR:
Azure/azure-sdk-for-go#6368

[azuresdkci]

Can one of the admins verify this patch?

[yaohaizh]

/azp run

[azure-pipelines]

Azure Pipelines successfully started running 2 pipeline(s).

[yaohaizh]

@ruowan, do you know what the error is: https://dev.azure.com/azure-sdk/public/_build/results?buildId=185539&view=logs&j=8d2f9c49-cd83-5a9d-f3fe-2fd651afa742&t=43324f1f-6724-5d61-785f-f0ac9fd256a1&l=4938

[ruowan]

It's model validation error. @raych1 Could you please take a look at this error.

[raych1]

@yaohaizh , those model validation errors are there before and are not caused by this PR change.
@jlichwa, I would suggest to fix those errors in separate PR otherwise these issues will appear in every future PR.

[yaohaizh]

@jlichwa Please fix the model validation errors in another PR since the previous swagger spec doesn't have the correct value.

[jlichwa]

@jlichwa Please fix the model validation errors in another PR since the previous swagger spec doesn't have the correct value.

Ok I will reach out to engineering team. I was updating this file only for documentation purposes - so the docs generated from it are clearly describing paramaters.