diff --git a/FAQ.md b/FAQ.md
index 91dea0cf1..6654d0e03 100644
--- a/FAQ.md
+++ b/FAQ.md
@@ -499,9 +499,17 @@ Now push the new branch to your forked GitHub repo with `git push -u origin BRAN
 
 Once the branch is available and synced between the RaspiBlitz GitHub repo, your forked GitHub repo and your local computer git repo, you can start developing.
 
-## How can I sync a branch of my forked with my local RaspiBlitz?
+## How can I sync a branch of my forked GitHub with my local RaspiBlitz?
 
-You need to know that there is a git copy of the original RaspiBlitz GitHub repo on your physical RaspiBlitz in the folder `/home/admin/raspiblitz`. If you change into that folder and run `git remote -v` you can see the set origin repo.
+Since v1.5 of RaspiBlitz there is an easy way thru the SSH menus: Under `MAIN MENU > UPDATE > PATCH` you have the option to change the GitHub Reposity and and Branch to sync with. You change the GitHub Reposity by setting the GutHub username where you forked the Repo.
+
+So for example: If you forked the RaspiBlitz project (rootzoll/raspiblitz) on GitHub and your GitHub project page is now called: https://github.com/raumi75/raspiblitz ... then justchange the Repo to sync/patch with to your username `raumi75`. 
+
+Now you can use the `Patch/Sync RaspiBlitz with GitHub Repo` to easily keep your RaspiBlitz in sync with your forked repository and develop your own customizations and features.
+
+Background info and doing it manually:
+
+There is a git copy of the original RaspiBlitz GitHub repo on your physical RaspiBlitz in the folder `/home/admin/raspiblitz`. If you change into that folder and run `git remote -v` you can see the set origin repo.
 
 You need to change that origin repo to your forked repo. You do that with:
 ```