[ISV-4897] Documentation fix and update (#669)

Author: mantomas

docs/README.md

@@ -25,15 +25,15 @@ If you have an existing Operator read our contribution guidelines on how to [ope
 
 ## Contributing Guide
 
-- [Prerequisites](contributing-prerequisites.md)
-- [Where to place operator](contributing-where-to.md)
-- [Creating pull request (PR)](contributing-via-pr.md)
-- [Operator Publishing / Review settings](operator-ci-yaml.md)
-- [OKD/OpenShift Catalogs criteria and options](packaging-required-criteria-ocp.md)
+- [Prerequisites](users/contributing-prerequisites.md)
+- [Where to place operator](users/contributing-where-to.md)
+- [Creating pull request (PR)](users/contributing-via-pr.md)
+- [Operator Publishing / Review settings](users/operator-ci-yaml.md)
+- [OKD/OpenShift Catalogs criteria and options](users/packaging-required-criteria-ocp.md)
 
 ## Test and release process for the Operator
 
-Refer to the [operator pipeline documentation](docs/pipelines_overview.md) .
+Refer to the [operator pipeline documentation](users/pipelines_overview.md) .
 
 ## IMPORTANT NOTICE
 

docs/users/contributing-via-pr.md

@@ -1,15 +1,15 @@
-# Submitting your Operator via Pull Requests (PR) in community operators project
+# Submitting your Operator via Pull Requests (PR)
 
 ## Overview
 To submit an operator one has to do these steps
 
-1. Fork project `https://github.com/redhat-openshift-ecosystem/community-operators-prod`
-1. Make a pull request
+1. Fork project based on desired [Operator Repository](./pipelines_overview.md#operator-repositories)
 1. Place the operator in the target directory. [More info](./contributing-where-to.md)
     - operators
 1. Configure `ci.yaml` file. [More info](./operator-ci-yaml.md)
     - Setup reviewers
     - Operator versioning strategy
+1. Make a pull request
 1. Verify tests and fix problems, if possible
 1. Ask for help in the PR in case of problems