added a drawing to clarify the workflow for syncing

Author: ekrempel

additional-material/keeping-your-fork-synced-with-this-repository.md

@@ -1,6 +1,8 @@
 # Keeping your fork synced with this repository
 
-First, the flow for a full sync should be understood. In this schema, there are 3 different repos: my public repo on Github `github.com/Roshanjossey/first-contributions/`, your fork of the repo on GitHub `github.com/Your-Name/first-contributions/` and your local machine's repo from which you are suppose to work. 
+First, the flow for a full sync should be understood. In this schema, there are 3 different repos: my public repo on Github `github.com/Roshanjossey/first-contributions/`, your fork of the repo on GitHub `github.com/Your-Name/first-contributions/` and your local machine's repo from which you are suppose to work. This kind of cooperation is typical for open source projects and called `Triangle Workflows`.
+
+<img align="right" width="300" src="assets/triangle_workflow.png" alt="triangle workflow" />
 
 To keep your two repos up-to-date with my public repo, our first move is to fetch and merge the public repo with your local machine's repo.
 Our second move will be to push your local repo to your GitHub fork. As you've seen earlier, it's only from your fork that you can ask for a "pull request". So your GitHub fork is the last repo to be updated. (A drawing should be inserted here for clarity)