Merge pull request #228439 from Naveenommi-MSFT/patch-27

(AzureCXP) fixes MicrosoftDocs/azure-docs#105549

Author: prmerger-automator[bot]

articles/machine-learning/how-to-manage-registries.md

@@ -40,7 +40,7 @@ You need to decide the following information carefully before proceeding to crea
 
 Consider the following factors before picking a name.
 * Registries are meant to facilitate sharing of ML assets across teams within your organization across all workspaces. Choose a name that is reflective of the sharing scope. The name should help identify your group, division or organization. 
-* Registry unique with your organization (Azure Active Directory tenant). It's recommended to prefix your team or organization name and avoid generic names. 
+* Registry name is unique with your organization (Azure Active Directory tenant). It's recommended to prefix your team or organization name and avoid generic names. 
 * Registry names can't be changed once created because they're used in IDs of models, environments and components that are referenced in code. 
   * Length can be 2-32 characters. 
   * Alphanumerics, underscore, hyphen are allowed. No other special characters. No spaces - registry names are part of model, environment, and component IDs that can be referenced in code.  
@@ -193,4 +193,4 @@ Microsoft.MachineLearningServices/registries/delete | Allows the user to delete
 
 ## Next steps
 
-* [Learn how to share models, components and environments across workspaces with registries (preview)](./how-to-share-models-pipelines-across-workspaces-with-registries.md)
+* [Learn how to share models, components and environments across workspaces with registries (preview)](./how-to-share-models-pipelines-across-workspaces-with-registries.md)