summaryrefslogtreecommitdiff
diff options
context:
space:
mode:
authorFrancesco Borzì <borzifrancesco@gmail.com>2021-08-15 18:04:00 +0200
committerGitHub <noreply@github.com>2021-08-15 18:04:00 +0200
commitfe9db614086eb20d21727aefd6228779f57b3833 (patch)
treed245cab8424afa7072ae2761332e1f7776a4bd07
parentfcd592283e077d0ae66ba5b7205454bcc31971e4 (diff)
downloadwiki-fe9db614086eb20d21727aefd6228779f57b3833.tar.gz
wiki-fe9db614086eb20d21727aefd6228779f57b3833.tar.bz2
wiki-fe9db614086eb20d21727aefd6228779f57b3833.zip
fix: bad copy paste
-rw-r--r--docs/how-to-create-a-db-pr.md4
1 files changed, 2 insertions, 2 deletions
diff --git a/docs/how-to-create-a-db-pr.md b/docs/how-to-create-a-db-pr.md
index 861488b..4350be9 100644
--- a/docs/how-to-create-a-db-pr.md
+++ b/docs/how-to-create-a-db-pr.md
@@ -8,7 +8,7 @@ This is a simplified guide to easily create PRs containing DB fixes (SQL code) w
an easier alternative to the [traditional way of creating PRs](https://www.azerothcore.org/wiki/how-to-create-a-pr).
If you want to submit C++ or other non-SQL kind of fixes, please follow the other guide.
-## Do only ONCE: create and clone your AzerothCore fork
+## Do only ONCE: create your AzerothCore fork
You need to be signed on [github.com](https://github.com/). If you don't have an account yet, create one.
@@ -123,4 +123,4 @@ It's also a good practice to check the "File changes" tab to see that everything
**NOTE:** We do not respond well to leechers! If your fix comes from another organization or person
you should ALWAYS give credit to the original author and commit.
-That's it! \ No newline at end of file
+That's it!