Specified develop branch as working branch in the dev guide.

Signed-off-by: Zsolt Gyulai (zgyulai) <zsolt.gyulai@quest.com>

Author: zsoltgyulai94

doc/_dev-guide/chapter_5/section_7.md

@@ -22,7 +22,8 @@ guidelines the following:
     message you submit.
     Signing off on commits enables users to affirm that a commit complies with the rules and licensing of a repository. This, in the case of {{ site.product.short_name }}, means that you accept our coding and contribution standards described in the Contribution section, and accept that your code will be published with a `GPLv2` license.
  5. Always create a separate branch for the pull request, forked off
-    from the appropriate {{ site.product.short_name }} branch.
+    from the {{ site.product.short_name }} `develop` branch.
+   The pull requests you create should always point to and be merged into the `develop` branch. Do not make PRs and try to merge into the `master` branch.
  6. If your patch should be applied to multiple branches, submit
     against the latest one only, and mention which other branches are
     affected. There is no need to submit pull requests for each