Fix inconsistent alerts by using the markdown notation - part 2 (#35221)

Co-authored-by: Alex Nguyen <150945400+nguyenalex836@users.noreply.github.com>

content/get-started/using-git/about-git-rebase.md

@@ -19,11 +19,8 @@ Typically, you would use `git rebase` to:
 * Combine multiple commits into one
 * Delete or revert commits that are no longer necessary
 
-{% warning %}
-
-**Warning**: Because changing your commit history can make things difficult for everyone else using the repository, it's considered bad practice to rebase commits when you've already pushed to a repository. To learn how to safely rebase, see "[AUTOTITLE](/pull-requests/collaborating-with-pull-requests/incorporating-changes-from-a-pull-request/about-pull-request-merges)."
-
-{% endwarning %}
+> [!WARNING]
+> Because changing your commit history can make things difficult for everyone else using the repository, it's considered bad practice to rebase commits when you've already pushed to a repository. To learn how to safely rebase, see "[AUTOTITLE](/pull-requests/collaborating-with-pull-requests/incorporating-changes-from-a-pull-request/about-pull-request-merges)."
 
 ## Rebasing commits against a branch
 

content/get-started/using-git/about-git-subtree-merges.md

@@ -101,11 +101,8 @@ The best way to explain subtree merges is to show by example. We will:
 
 Although we've only added one subproject, any number of subprojects can be incorporated into a Git repository.
 
-{% tip %}
-
-**Tip**: If you create a fresh clone of the repository in the future,  the remotes you've added will not be created for you. You will have to add them again using [the `git remote add` command](/get-started/getting-started-with-git/managing-remote-repositories).
-
-{% endtip %}
+> [!TIP]
+> If you create a fresh clone of the repository in the future,  the remotes you've added will not be created for you. You will have to add them again using [the `git remote add` command](/get-started/getting-started-with-git/managing-remote-repositories).
 
 ## Synchronizing with updates and changes
 

content/get-started/using-git/splitting-a-subfolder-out-into-a-new-repository.md

@@ -14,11 +14,8 @@ versions:
 shortTitle: Splitting a subfolder
 ---
 
-{% note %}
-
-**Note:** You need Git version 2.22.0 or later to follow these instructions, otherwise `git filter-repo` will not work.
-
-{% endnote %}
+> [!NOTE]
+> You need Git version 2.22.0 or later to follow these instructions, otherwise `git filter-repo` will not work.
 
 If you create a new clone of the repository, you won't lose any of your Git history or changes when you split a folder into a separate repository.  However, note that the new repository won't have the branches and tags of the original repository.
 
@@ -43,11 +40,8 @@ If you create a new clone of the repository, you won't lose any of your Git hist
 
    {% windows %}
 
-   {% tip %}
-
-   **Tip:** Windows users should use `/` to delimit folders.
-
-   {% endtip %}
+   > [!TIP]
+   > Windows users should use `/` to delimit folders.
 
    {% endwindows %}
 
@@ -71,11 +65,8 @@ If you create a new clone of the repository, you won't lose any of your Git hist
 
    ![Screenshot of the "Quick Setup" header in a repository. Next to the remote URL, an icon of two overlapping squares is highlighted with an orange outline.](/assets/images/help/repository/copy-remote-repository-url-quick-setup.png)
 
-   {% tip %}
-
-   **Tip:** For information on the difference between HTTPS and SSH URLs, see "[AUTOTITLE](/get-started/getting-started-with-git/about-remote-repositories)."
-
-   {% endtip %}
+   > [!TIP]
+   > For information on the difference between HTTPS and SSH URLs, see "[AUTOTITLE](/get-started/getting-started-with-git/about-remote-repositories)."
 
 1. Add a new remote name with the URL you copied for your repository. For example, `origin` or `upstream` are two common choices.