fixes release 0.7 (#25)

*fiexes release 0.7

Author: wiewiurdp

README.md

@@ -2,7 +2,7 @@
 
 ## Community
 
-* Get Ergonode support on [**Slack**](https://ergonode.slack.com) and [**email**](team@ergonode.com).
+* Get Ergonode support on [**Slack**](https://ergonode.slack.com) or send us email **team@ergonode.com**.
 * Follow us on [**GitHub**](https://github.com/ergonode), [**Twitter**](https://twitter.com/ergonode) and [**Facebook**](https://www.facebook.com/ergonode),  
 
 ## Quick start

docs/_sidebar.md

@@ -1,4 +1,4 @@
-[**Ergonode** ](index.md)
+**Ergonode**
 * [**Basic information**](basic_info.md)
 * [**Backend**](backend.md)
     * [Architecture](backend/architecture.md)

docs/backend/cookbook/new_condition.md

@@ -371,4 +371,4 @@ and in the api ```/api/v1/EN/dictionary/conditions``` endpoint you should have
 }
  ``` 
 
-full code example you can find in the   [product-sku-condition-module](https://github.com/wiewiurdp/docs/tree/master/docs/backend/cookbok/examples/product-sku-condition-module)
+You can find code examples under namespace `Ergonode\Condition`

docs/basic_info.md

@@ -7,4 +7,3 @@ Ergonode is under [OSL-3.0](https://opensource.org/licenses/osl-3.0.php) license
 ## Road map
 
 [**Click here**](https://trello.com/b/DSWyaTlL/ergonode-product-roadmap)
-~~~~

docs/community/contribution.md

@@ -22,15 +22,15 @@ The Ergonode development team will review all issues and contributions submitted
 ### Contribution requirements
 ---
 
-1. Contributions must adhere to the [Coding standards](frontend/quality?id=coding-standards).
+1. Contributions must adhere to the [Coding standards](backend/coding_standards.md).
 
 2. Pull requests (PRs) must be accompanied by a meaningful description of their purpose. Comprehensive descriptions increase the chances of a pull request being merged quickly and without additional clarification requests. Description can be delivered as an issue linked to PR.
 
 3. PRs which include bug fixes must be accompanied with a step-by-step description of how to reproduce the bug. This also can be delivered as a linked issue.
 
 4. PRs which include new logic or new features must be submitted along with:
 
-    a. Unit/integration [test](frontend/quality?id=tests) coverage.
+    a. Unit/integration [test](backend/tests.md) coverage.
 
     b. PRD - Product Requirement Document that contains all necessary background of purpose and proposed implementations.