(docs): Changing the danger admonitions into note.

Author: dericksozo

docs/getting-started/smart-git-sync.md

@@ -62,7 +62,7 @@ For example, Amplication will base the `amplication` branch from `main` if your
 
 You can merge Amplication-made changes by merging pull requests created by Amplication from the `amplication` branch to your repository's default branch.
 
-:::warning
+:::note
 **Do not delete the `amplication` branch**.
 
 Do not modify the `amplication` branch, except to resolve conflicts. Handle conflicts directly on the `amplication` branch. Avoid creating new commits or merging changes from other branches to prevent bugs and inconsistencies.

docs/getting-started/sync-with-bitbucket.md

@@ -126,7 +126,7 @@ Amplication creates pull requests from the `amplication` branch into your reposi
 Amplication triggers the creation of a commit on the changed files whenever a new build is performed on a project.
 The changed files are all the files that were added, removed, or changed from the last build.
 
-:::warning
+:::note
 **Do not delete the `amplication` branch**.
 
 Do not modify the `amplication` branch, except to resolve conflicts. Handle conflicts directly on the `amplication` branch. Avoid creating new commits or merging changes from other branches to prevent bugs and inconsistencies.

docs/getting-started/sync-with-github.md

@@ -142,7 +142,7 @@ Now let's review what happens from GitHub's side when Amplication generates a ne
 Amplication triggers the creation of a commit on the changed files whenever a new build is performed on a project.
 The changed files are all the files that were added, removed, or changed from the last build.
 
-:::warning
+:::note
 **Do not delete the `amplication` branch**.
 
 Do not modify the `amplication` branch, except to resolve conflicts. Handle conflicts directly on the `amplication` branch. Avoid creating new commits or merging changes from other branches to prevent bugs and inconsistencies.