diff --git a/CONTRIBUTING.md b/CONTRIBUTING.md
index 250db4a22d..a85436ef57 100644
--- a/CONTRIBUTING.md
+++ b/CONTRIBUTING.md
@@ -6,6 +6,7 @@ Greetings traveller!
 
 * [Akka Contributor License Agreement](www.typesafe.com/contribute/cla)
 * [Akka Issue Tracker](http://doc.akka.io/docs/akka/current/project/issue-tracking.html)
+* [Scalariform](https://github.com/mdr/scalariform)
 
 ##Workflow##
 
@@ -13,9 +14,10 @@ Greetings traveller!
    we won't accept anything from anybody who has not signed it.
 1. Find-or-create a ticket in the issue tracker
 2. Assign that ticket to yourself
-3. Create a local branch with the following name format: wip-X-Y
+3. Create a local branch with the following name format: wip-X-Y-Z
    where the X is the number of the ticket in the tracker,
-   and Y is your initials or similar.
+   and Y is some brief keywords of the ticket title and Z is your initials or similar.
+   Example: wip-2373-add-contributing-md-√
 4. Do what needs to be done (with tests and docs if applicable).
    Your branch should pass all tests before going any further.
 5. Push the branch to your clone of the Akka repository
@@ -32,4 +34,25 @@ Greetings traveller!
 11. Pull Request is either merged by the Akka committers,
     or rejected, and the associated ticket will be updated to
     reflect that.
-12. Delete the local and remote wip-X-Y
\ No newline at end of file
+12. Delete the local and remote wip-X-Y-Z
+
+##Code Reviews##
+
+Akka utilizes peer code reviews to streamline the codebase, reduce the defect ratio,
+increase maintainability and spread knowledge about how things are solved.
+
+Core review values:
+
+* Rule: [The Boy Scout Rule](http://programmer.97things.oreilly.com/wiki/index.php/The_Boy_Scout_Rule)
+  Why: Small improvements add up over time, keeping the codebase in shape.
+* Rule: [Don't Repeat Yourself](http://programmer.97things.oreilly.com/wiki/index.php/Don't_Repeat_Yourself)
+  Why: Repetitions are not maintainable, keeping things DRY makes it easier to fix bugs and refactor,
+  since you only need to apply the correction in one place, or perform the refactoring at one place.
+* Rule: Feature tests > Integration tests > Unit tests
+  Why: Without proving that a feature works, the code is only liability,
+       Without proving that a feature works with other features, the code is of limited value,
+       Without proving the individual parts of a feature works, the code is harder to debug.
+
+##Source style##
+
+Akka uses [Scalariform](https://github.com/mdr/scalariform) to enforce some of the code style rules.
\ No newline at end of file