update the note

Author: mumian

articles/azure-resource-manager/resource-manager-quickstart-create-templates-use-the-portal.md

@@ -76,7 +76,7 @@ Many experienced template developers use this method to generate templates when
 The Azure portal can be used to perform some basic template editing. In this quickstart, you use a portal tool called *Template Deployment*. *Template Deployment* is used in this tutorial so you can complete the whole tutorial using one interface - the Azure portal. To edit a more complex template, consider using [Visual Studio Code](./resource-manager-quickstart-create-templates-use-visual-studio-code.md),  which provides richer edit functionalities.
 
 > ![IMPORTANT]
-> Template Deployment has not been updated for a while. It is not recommended to use this feature in production. To store templates, consider using Azure Storage Account or [Git](./resource-manager-tutorial-use-azure-pipelines.md).
+> Template Deployment provides an interface for testing simple templates. It is not recommended to use this feature in production. Instead, store your templates in an Azure storage account, or a source code repository like GitHub.
 
 Azure requires that each Azure service has a unique name. The deployment could fail if you entered a storage account name that already exists. To avoid this issue, you modify the template to use a template function call `uniquestring()` to generate a unique storage account name.