[BE-708] Online docs issues (#54)

* updated links

Signed-off-by: nfrunza <nfrunza@gmail.com>

CONTRIBUTING.md

@@ -43,8 +43,9 @@ _In general a commit serves a single purpose and diffs should be easily comprehe
 For this reason do not mix any formatting fixes or code moves with actual code changes._
 1. **Commit your changes** see [How to Write a Git Commit Message](https://chris.beams.io/posts/git-commit/) article by Chris Beams.
 1. **Test your changes** locally before pushing to ensure that what you are proposing is not breaking
-another part of the software. Running the `./main.sh clean && ./main.sh install && ./main.sh test` command locally will help you
-to be confident that your changes will pass CI tests once pushed as a Pull Request.
+another part of the software.
+Running the ```./main.sh clean && ./main.sh install && ./main.sh test``` command locally will help you to be confident that your changes will
+pass CI tests once pushed as a Pull Request.
 1. **Push your changes** to your remote fork.
 1. **Create a pull-request** (PR) on the Hyperledger Explorer repository. If the PR addresses an existing Jira issue,
 include the issue number in the PR title in square brackets (for example, `[BE-333]`).

docs/source/CONTRIBUTING.rst

@@ -15,8 +15,8 @@ project, you will need a `Linux Foundation account <https://identity.linuxfounda
 
 You will need to use your LF ID to access to all the Hyperledger community tools, including:
 
- * `Jira <https://jira.hyperledger.org>`__.
- * `RocketChat <https://chat.hyperledger.org>`__.
+ * `Jira <https://jira.hyperledger.org/projects/BE/issues>`__.
+ * `RocketChat <https://chat.hyperledger.org/channel/hyperledger-explorer>`__.
  * `Mailing list <https://lists.hyperledger.org/g/explorer>`__.
 
 
@@ -62,6 +62,13 @@ Verified Docker versions supported:
 - `Docker Compose 1.14.0 <https://docs.docker.com/compose>`__
 
 
+Working on fixing issues and working stories
+~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
+
+Review the `issues list <https://jira.hyperledger.org/projects/BE/issues>`__ and find something that interests you.
+Start with something relatively straight forward and achievable, and that no one is already assigned. If no one is assigned, then assign the issue
+to yourself. Please be considerate and rescind the assignment if you cannot finish in a reasonable time, or add a comment saying that you are
+still actively working the issue if you need a little more time.
 
 Submitting your fix
 ~~~~~~~~~~~~~~~~~~~
@@ -71,28 +78,14 @@ provide a fix, we would welcome that gladly! Please assign the JIRA issue to
 yourself, then you can submit a change request (PR), please follow guidance provided by `CONTRIBUTING.md <https://github.com/hyperledger/blockchain-explorer/blob/master/CONTRIBUTING.md>`__.
 
 
-Working on fixing issues and working stories
-~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
-
-Review the `issues
-list <https://jira.hyperledger.org/secure/RapidBoard.jspa?rapidView=155&view=planning.nodetail>`__ and find
-something that interests you.
-Start with something relatively straight forward and
-achievable, and that no one is already assigned. If no one is assigned,
-then assign the issue to yourself. Please be considerate and rescind the
-assignment if you cannot finish in a reasonable time, or add a comment
-saying that you are still actively working the issue if you need a
-little more time.
-
-
 Copyright Notices
+~~~~~~~~~~~~~~~~~~~
 
 There should be a single LICENSE file in the top-level directory that contains the full text of the Apache License `here <http://www.apache.org/licenses/LICENSE-2.0>`__.
 
 
 
 
-
 .. note:: In the individual files, please use the following line:
 
 

docs/source/architecture/sync_configuration.rst

@@ -48,7 +48,7 @@ Configuration
         :title: Run host (Standalone)
 
 							  * From new terminal (if Sync Process in Standalone).
-									
+
 										* ``cd blockchain-explorer/``
 										* ``./syncstart.sh`` (it will have the sync node up).
 										* ``./syncstop.sh`` (it will stop the sync node).
@@ -70,7 +70,7 @@ Configuration
 
 .. attention::
 
-			* Please restart Explorer if any changes made to explorerconfig.json.
+			* Please restart Explorer if any changes made to `explorerconfig.json <https://github.com/hyperledger/blockchain-explorer/blob/master/app/explorerconfig.json>`__.
 
 			  * If the Hyperledger Explorer was used previously in your browser be sure to clear the cache before relaunching.
 			  * If Hyperledger Fabric network is deployed on other machine, please toggle ``DISCOVERY_AS_LOCALHOST`` in ``start.sh / syncstart.sh to 'false'``.
@@ -79,15 +79,3 @@ Configuration
 
 
 
-
-
-
-
-
-
-
-
-
-
-
-.. TODO

docs/source/architecture/websockets.rst

@@ -16,4 +16,3 @@ new block details is provided in the notification panel.
 .. raw:: html
      :file: ./websockets.html
 
-.. TODO

docs/source/dev-setup/devenv.rst

@@ -62,7 +62,7 @@ This facilitates social contribution, easy testing, and peer review.
 
 To contribute changes, use the following workflow:
 
-* `Fork the repository <https://github.com/hyperledger/blockchain-explorer/form>`__.
+* `Fork the repository <https://github.com/hyperledger/blockchain-explorer/fork>`__.
 * Clone your fork to your computer.
 * Create a topic branch and name it appropriately. Starting the branch name with the issue number is a good practice and a reminder to fix only one issue in a Pull-Request (PR).
 * Make your changes, adhering to the documentation conventions described below. In general a commit serves a single purpose and diffs should be easily comprehensible. For this reason do not mix any formatting fixes or typo fixes with actual documentation changes.