Update containertypes.md

Author: ShreyasSar26

docs/embedded/concepts/app-concepts/containertypes.md

@@ -44,7 +44,7 @@ The following restrictions are applied to container type in the trial status:
 
 ## Standard/Non-trial use
 
-A standard container type, by definition, has a billing profile associated with it and can be either regular billed or direct to consumer billed. A standard container type is created using the [New-SPOContainerType](https://learn.microsoft.com/en-us/powershell/module/sharepoint-online/new-spocontainertype?view=sharepoint-ps) cmdlet . In case of regular billing, the next step after creation is the addition of a billing profile using the [Add-SPOContainerTypeBilling](https://learn.microsoft.com/en-us/powershell/module/sharepoint-online/add-spocontainertypebilling?view=sharepoint-ps) cmdlet. With the use of `-IsPassThroughBilling`, you can create a direct to customer billed container type. There is no need to attach a billing profile in case this case. You need the following to create a container type in the standard status:
+A standard container type, by definition, has a billing profile associated with it and can be either regular billed or direct to consumer billed. A standard container type is created using the [New-SPOContainerType](/powershell/module/sharepoint-online/new-spocontainertype) cmdlet . In case of regular billing, the next step after creation is the addition of a billing profile using the [Add-SPOContainerTypeBilling](/powershell/module/sharepoint-online/add-spocontainertypebilling) cmdlet. With the use of `-IsPassThroughBilling`, you can create a direct to customer billed container type. There is no need to attach a billing profile in case this case. You need the following to create a container type in the standard status:
 
 - An Azure subscription and Resource Group must be present in the Azure portal, in case of regular billed. 
 - An App registration must be created in Microsoft Entra ID