fix: Replace Tip with Alert style [!TIP]

Author: nschonni

docs/organizations/projects/create-project.md

@@ -211,7 +211,8 @@ You can create a project from Team Explorer after you have connected to an on-pr
 
     ![ALM\_EXL\_Connect](_img/IC680074.png)
 
-    >**Tip:**  If you are running Team Explorer from a server that hosts SharePoint Products and SQL Server Reporting Services, you might need to run Visual Studio as an administrator.
+    > [!TIP]
+    > If you are running Team Explorer from a server that hosts SharePoint Products and SQL Server Reporting Services, you might need to run Visual Studio as an administrator.
 
 5. If it's your first time connecting to TFS, you need to add TFS to the list of recognized servers.
 

docs/pipelines/archive/news/2016.md

@@ -66,7 +66,8 @@ When a minor version is released (for example, 1.2 to 1.3), you get that change
 
 If you select a version named something such as <strong>1.* (preview)</strong>, keep in mind that this version is still under development and might have known problems.
 
-> **Tip:** In a build definition you've got a few options to test a new major version of a task:
+> [!TIP]
+> In a build definition you've got a few options to test a new major version of a task:
 >  * If you change the version and have problems, you can revert the change from the history tab.
 >  * Clone the build definition and test the cloned definition with the new major task version.
 
@@ -230,8 +231,9 @@ Does your team have a lot of build definitions. You can now use folders to keep
 
 ![Manage folders](_img/2016/08/manage-folders.png)
 
-> **Tip:** Have a batch of definitions that need the same permissions? Put them in a folder and then you can give permissions to the folder.
- ![Manage folders](_img/2016/08/folder-permissions.png)
+> [!TIP]
+> Have a batch of definitions that need the same permissions? Put them in a folder and then you can give permissions to the folder.
+> ![Manage folders](_img/2016/08/folder-permissions.png)
 
 ### Lots more data about the build
 

docs/pipelines/archive/release/previous-version/install-release-management/install-deployment-agent.md

@@ -30,10 +30,11 @@ for these has sufficient permissions to do whatever tasks are required for
 the release. The service account you use for the deployment agents is 
 automatically added to Release Management.
 
-***Tip:*** _As good practice, do not install the deployment agent on the 
-same machine as the Release Management server. If you do install the two on 
-the same machine and you need to upgrade, uninstall the server before you 
-uninstall the deployment agent._ 
+> [!TIP]
+> As good practice, do not install the deployment agent on the 
+> same machine as the Release Management server. If you do install the two on 
+> the same machine and you need to upgrade, uninstall the server before you 
+> uninstall the deployment agent. 
  
 ## Install and configure the Microsoft deployment agent
 
@@ -42,8 +43,9 @@ uninstall the deployment agent._
    where you will install the agent. You must also be a member of the 
    **Release Manager** role in Release Management.
 
-   ***Tip:*** _Do you need to add teammates to the **Release Manager** role 
-   in Release Management? See [Add users to Release Management](../add-users-and-groups.md)._
+   > [!TIP]
+   > Do you need to add teammates to the **Release Manager** role 
+   > in Release Management? See [Add users to Release Management](../add-users-and-groups.md).
 
 2. If you have not already downloaded the deployment agent, 
    **[do this now](https://visualstudio.microsoft.com/downloads/download-visual-studio-vs)**.
@@ -64,8 +66,9 @@ uninstall the deployment agent._
 
 4. Restart your computer, if prompted, and then choose **Launch**.
 
-   ***Tip:*** _If you join the Visual Studio Experience Improvement Program, 
-   you can **[opt out](../manage-your-release.md#optout)** at any time._ 
+   > [!TIP]
+   > If you join the Visual Studio Experience Improvement Program,
+   > you can **[opt out](../manage-your-release.md#optout)** at any time.
 
 5. Specify the account to run the Microsoft Deployment Agent Windows 
    service and the URL of the Release Management Server. If you use a user 

docs/pipelines/archive/release/previous-version/install-release-management/install-server-and-client.md

@@ -33,12 +33,13 @@ not removed. Then install the latest server and client. When you configure
 the latest update for your Release Management server, use the same SQL Server 
 instance that you used before for the database server.
 
-***Tip:*** _If you installed TFS Express or basic, you have an instance of 
-SQL Server Express available to you. If you installed TFS, you already have 
-the necessary permissions on the SQL Server. If you don't know if you're 
-using SQL Express, look at the **Application Tier** node in the TFS 
-administration console. Scroll down to **Data Tier Summary** and look for 
-**SQLServerExpress** to confirm._
+> [!TIP]
+> If you installed TFS Express or basic, you have an instance of
+> SQL Server Express available to you. If you installed TFS, you already have
+> the necessary permissions on the SQL Server. If you don't know if you're
+> using SQL Express, look at the **Application Tier** node in the TFS
+> administration console. Scroll down to **Data Tier Summary** and look for
+> **SQLServerExpress** to confirm.
 
 <a name="installserver"></a>
 ## Install the Release Management server
@@ -67,8 +68,9 @@ administration console. Scroll down to **Data Tier Summary** and look for
 
 4. Restart your computer, if prompted, and then choose **Launch**.
 
-   ***Tip:*** _If you join the Visual Studio Experience Improvement Program, 
-   you can **[opt out](../manage-your-release.md#optout)** at any time._ 
+   > [!TIP]
+   > If you join the Visual Studio Experience Improvement Program,
+   > you can **[opt out](../manage-your-release.md#optout)** at any time.
 
 5. Specify the SQL Server instance to host the Release Management Server 
    database and then choose **Test** to verify connectivity. Accept the default 
@@ -121,18 +123,20 @@ administration console. Scroll down to **Data Tier Summary** and look for
 
 1. Restart your computer, if prompted, and then choose **Launch**.
 
-   ***Tip:*** _If you join the Visual Studio Experience Improvement Program, 
-   you can **[opt out](../manage-your-release.md#optout)** at any time._ 
+   > [!TIP]
+   > If you join the Visual Studio Experience Improvement Program,
+   > you can **[opt out](../manage-your-release.md#optout)** at any time.
 
 1. Enter the name of the Release Management server. If you're installing the 
    client on the same computer that is running Release Management server, you 
    can use **localhost** to connect to the server.
 
    ![Connecting the client to the server](_img/install-server-client-06.png)
 
-   ***Tip:*** _If you changed any of the default options in your Release 
-   Management server setup, you can change the protocol or port number here so 
-   that you can connect to the server._
+   > [!TIP]
+   > If you changed any of the default options in your Release
+   > Management server setup, you can change the protocol or port number here so
+   > that you can connect to the server.
 
 ## Related topics
 

docs/pipelines/build/options.md

@@ -56,7 +56,8 @@ For an example, see [Use a script to customize your build pipeline](../scripts/p
 
 Select the [pool](../agents/pools-queues.md) that's attached to the pool that contains the agents you want to run this pipeline.
 
-**Tip:**  If your code is in Azure Pipelines and you run your builds on Windows, in many cases the simplest option is to use the [Hosted pool](../agents/hosted.md).
+> [!TIP]
+> If your code is in Azure Pipelines and you run your builds on Windows, in many cases the simplest option is to use the [Hosted pool](../agents/hosted.md).
 
 ## Build job authorization scope
 

docs/pipelines/repos/pipeline-options-for-git.md

@@ -365,7 +365,8 @@ In these cases this option can help you conserve network and storage resources.
 
 After you select the check box to enable this option, in the **Depth** box specify the number of commits.
 
-> **Tip:** The `Agent.Source.Git.ShallowFetchDepth` variable mentioned below also works and overrides the check box controls. This way you can modify the setting when you queue the build.
+> [!TIP]
+> The `Agent.Source.Git.ShallowFetchDepth` variable mentioned below also works and overrides the check box controls. This way you can modify the setting when you queue the build.
 
 ::: moniker-end
 

docs/report/admin/add-a-report-server.md

@@ -80,7 +80,8 @@ After you confirm that you have an edition of SQL Server that supports reporting
 
 2.	Once your server has passed all the setup rules checks, pick the instance to add features to.   
 
-	**Tip:** If you upgraded from SQL Server Express, you'll have a named instance called SQLEXPRESS.  
+	  > [!TIP]
+    > If you upgraded from SQL Server Express, you'll have a named instance called SQLEXPRESS.  
 
 	![Add features to an existing instance](_img/installation-type.png)  
 
@@ -148,13 +149,15 @@ You'll need to add reporting in two places: to TFS itself, and then to your team
 
 	![Use the default name for the database](_img/reporting-warehouse.png)  
 
-	**Tip:** Because you're configuring reporting for the first time, the databases don't exist yet. They will be created when you finish the configuration process.
+    > [!TIP]
+    > Because you're configuring reporting for the first time, the databases don't exist yet. They will be created when you finish the configuration process.
 
 3. Provide the same server and instance information for **Analysis Services**, but use the default name for the analysis database (TFS_Analysis). Provide an account name and password for a data sources account, a special account you've created just for this purpose as described in [Service accounts and dependencies in TFS](/azure/devops/server/admin/service-accounts-dependencies-tfs). 
 
 	![You'll need to add the reader account information](_img/analysis-services.png)  
 
-	**Tip:** Test the connection before continuing.  
+    > [!TIP]
+    > Test the connection before continuing.  
 
 4.	For **Reports**, provide the server name and the instance name in **Server**, separated by a slash.  
 
@@ -169,7 +172,8 @@ You'll need to add reporting in two places: to TFS itself, and then to your team
 
 	![Edit the folder location to start configuring](_img/team-project-collections.png)  
 
-	**Tip:** If you don't see the **Reports Folder** tab, you might need to refresh or restart the administration console.  
+    > [!TIP]
+    > If you don't see the **Reports Folder** tab, you might need to refresh or restart the administration console.  
 
 6.	Unless you have reasons otherwise, use the example provided, and make sure you include the collection name.  
 

docs/repos/tfvc/_shared/personal-access-tokens.md

@@ -28,18 +28,20 @@ ms.topic: include
 
 6. When you're done, make sure to *copy the token*. You'll use this token as your password.
 
-   <img alt="Use token as the password for your git tools or apps" src="./_img/create-personal-access-token.png" style="border: 1px solid #CCCCCC" />
-
-	**Note: Remember that this token is your identity and acts as you when it's used. 
-	Keep your tokens secret and treat them like your password.**
-
-	**Tip:** To keep your token more secure, use credential managers 
-	so that you don't have to enter your credentials every time. 
-	Here are some recommended credential managers:
-    
-	*	Git: [Git Credential Manager for macOS and Linux](https://github.com/Microsoft/Git-Credential-Manager-for-Mac-and-Linux) 
-	or [Git Credential Manager for Windows](https://github.com/Microsoft/Git-Credential-Manager-for-Windows) 
-	(Requires [Git for Windows](https://www.git-scm.com/download/win))
-	*	NuGet: [NuGet Credential Provider](/azure/devops/artifacts/nuget/nuget-exe)
+    <img alt="Use token as the password for your git tools or apps" src="./_img/create-personal-access-token.png" style="border: 1px solid #CCCCCC" />
+
+    **Note: Remember that this token is your identity and acts as you when it's used. 
+	  Keep your tokens secret and treat them like your password.**
+
+    > [!TIP]
+    > To keep your token more secure, use credential managers
+    > so that you don't have to enter your credentials every time.
+
+    Here are some recommended credential managers:
+
+    *	Git: [Git Credential Manager for macOS and Linux](https://github.com/Microsoft/Git-Credential-Manager-for-Mac-and-Linux) 
+    or [Git Credential Manager for Windows](https://github.com/Microsoft/Git-Credential-Manager-for-Windows) 
+    (Requires [Git for Windows](https://www.git-scm.com/download/win))
+    *	NuGet: [NuGet Credential Provider](/azure/devops/artifacts/nuget/nuget-exe)
 
 7. When you don't need your token anymore, just revoke it to remove its access.

docs/repos/tfvc/add-command.md

@@ -20,8 +20,8 @@ monikerRange: '>= tfs-2015'
 
 Adds files and folders to version control.
 
->**Tip:**  
->Before you add files to version control, you should first set up the workspace on your dev machine. See [Workspace Command](workspace-command.md) or [Set up Team Foundation Version Control on your dev machine](set-up-team-foundation-version-control-your-dev-machine.md).  
+> [!TIP]
+> Before you add files to version control, you should first set up the workspace on your dev machine. See [Workspace Command](workspace-command.md) or [Set up Team Foundation Version Control on your dev machine](set-up-team-foundation-version-control-your-dev-machine.md).  
 
 **Requirements:** See [Permissions and groups reference](../../organizations/security/permissions.md).
 

docs/repos/tfvc/associate-file-type-file-comparison-tool.md

@@ -37,8 +37,9 @@ To perform this procedure, you must be a member of the **Administrators** or **U
 
 3.  In the **Extension** box, specify the extension (for example, .cpp) that you want to associate with your tool.
 
-	>**Tip:**  
-	>Specify `.*` if you want to associate all types of files with your tool.
+    > [!TIP]
+    > Specify `.*` if you want to associate all types of files with your tool.
+
 4.  In the **Operation** list, choose **Compare**.  
 5.  In the **Command** box, either type the path and name of your tool, or choose the ellipses (**...**) to locate and specify it. The result should resemble the following example:
 
@@ -51,8 +52,8 @@ To perform this procedure, you must be a member of the **Administrators** or **U
     -   **%6**: Label ("friendly name") of the source file.  
     -   **%7**: Label ("friendly name") of the target file.
 
-    >**Tip:**  
-    >For information about frequently used external tools and the arguments that they require, see the following page on the Microsoft website: [diff/merge configuration in Team Foundation - common Command and Argument values](http://go.microsoft.com/fwlink/?LinkID=200171).
+    > [!TIP]
+    > For information about frequently used external tools and the arguments that they require, see the following page on the Microsoft website: [diff/merge configuration in Team Foundation - common Command and Argument values](http://go.microsoft.com/fwlink/?LinkID=200171).
 
     **Use white space to delimit the arguments.**  
     For example, you might specify the following syntax to compare two files:

docs/repos/tfvc/branch-folders-files.md

@@ -35,10 +35,10 @@ As each version is released, the Main branch is branched into a new version bran
 
 You can perform a branching operation by using either **Source Control Explorer**, as this topic demonstrates, or the Branch command at a command prompt. For more information, see [Branch Command](branch-command.md).
 
->**Tip:**  
->Branching is an important and powerful technique for creating a parallel set of versions of your files. However, using branches can add complexity and cost to your project. For example, when you merge two branches, you may have to resolve conflicts.  
+> [!TIP]
+> Branching is an important and powerful technique for creating a parallel set of versions of your files. However, using branches can add complexity and cost to your project. For example, when you merge two branches, you may have to resolve conflicts.  
 >
->Before you create a branch, you should consider whether you can better meet your needs by applying a label. By applying a label, you can quickly and easily take a snapshot of the state of your files so that you can then later retrieve or build the files in that state. For more information, see [Use labels to take a snapshot of your files](use-labels-take-snapshot-your-files.md).
+> Before you create a branch, you should consider whether you can better meet your needs by applying a label. By applying a label, you can quickly and easily take a snapshot of the state of your files so that you can then later retrieve or build the files in that state. For more information, see [Use labels to take a snapshot of your files](use-labels-take-snapshot-your-files.md).
 
 ## Convert a Folder to a Branch
 

docs/repos/tfvc/create-work-workspaces.md

@@ -94,7 +94,8 @@ If your team has a large and complex codebase or if you want your workspace to c
 
 -   **Owner**: Only the owner of a workspace can use it.
 
-    >**Tip:**  Instead of changing the owner of your workspace when someone else needs to continue your work you can [suspend (or shelve)](suspend-your-work-manage-your-shelvesets.md) your work and then share the shelveset with them.
+    > [!TIP]
+    > Instead of changing the owner of your workspace when someone else needs to continue your work you can [suspend (or shelve)](suspend-your-work-manage-your-shelvesets.md) your work and then share the shelveset with them.
 
 -   **Computer**: This box identifies the dev machine where the workspace exists, and it is read-only. You cannot move a workspace from one computer to another. However, if the name of your dev machine has changed and you want that change to appear in this field, run [tf workspaces /updatecomputername](workspaces-command.md).
 

docs/repos/tfvc/day-life-alm-developer-suspend-work-fix-bug-conduct-code-review.md

@@ -65,8 +65,8 @@ Now that his workspace is clean, Peter drags the new task from **Available Work
 
         Alternatively, you can switch to a work item that you previously suspended by dragging it from under **Suspended Work**.
 
->**Tip:**
->  The currently In Progress work items link to your current code changes and Visual Studio state. To allow Visual Studio to help you organize your work, make sure that the appropriate items are in the In Progress state when you switch from one task to another.
+> [!TIP]
+> The currently In Progress work items link to your current code changes and Visual Studio state. To allow Visual Studio to help you organize your work, make sure that the appropriate items are in the In Progress state when you switch from one task to another.
 
 ## Investigate the bug
 
@@ -166,8 +166,8 @@ In her comments, Julia points out that the test is wrong. The allowable error sh
                 TestEqual(1000, 1000*1e-7, true); // Less than allowed error
                 TestEqual(1000, 1000*1e-5, false); // More than allowed error
 
->**Tip:**
->  Notice that the team members use the tests as a focus for discussion. If the tests are correct and sufficient, the code will be also. Unlike the code, each test represents a separate case. For this reason, the tests are often easier to discuss than the code.
+> [!TIP]
+> Notice that the team members use the tests as a focus for discussion. If the tests are correct and sufficient, the code will be also. Unlike the code, each test represents a separate case. For this reason, the tests are often easier to discuss than the code.
 
 ## To perform a code review![My Work page - code review item. Code Review page - Decline link, Comment, Decline button.](_img/day-life-alm-developer-suspend-work-fix-bug-conduct-code-review/IC591278.png)![Diff window. Code Review page - Accept link, Overall comment, code block comment](_img/day-life-alm-developer-suspend-work-fix-bug-conduct-code-review/IC592880.png)
 1.  In **Team Explorer**, on the **My Work** page, go to the **My Code Reviews & Requests** section and open the request.
@@ -240,8 +240,8 @@ The test passes once again:
 
 ![Unit Test Explorer showing passed test for equal](_img/day-life-alm-developer-suspend-work-fix-bug-conduct-code-review/IC675828.png)
 
->**Tip:**
->  To fix a bug, follow the same practice as in code development. Write a test that fails and then make the test pass. Check in the code and the tests only when the tests pass.
+> [!TIP]
+> To fix a bug, follow the same practice as in code development. Write a test that fails and then make the test pass. Check in the code and the tests only when the tests pass.
 
 Peter now turns his attention to the test case in which the bug was discovered. The steps to reproduce the bug are clearly described in the test case work item. He follows the steps and discovers that the invoices are correctly listed.