improved formatting and text style

Author: nakov

Content/Chapter-11-tricks-and-hacks/naming-elements-of-the-code/naming-elements-of-the-code.md

@@ -33,10 +33,10 @@ Here are some examples for **well named** variables:
 
 Here are some examples for **badly named variables**, even though the names are correct according to the C# compiler:
 
-* **`_firstName`** (starts with '\_')
-* **`last_name`** (contains '\_')
-* **`AGE`** (it is written in uppercase)
-* **`Start_Index`** (starts with an uppercase letter and contains '\_')
-* **`lastNegativeNumber_Index`** (contains '\_')
+* **`_firstName`** (starts with '`_`')
+* **`last_name`** (contains '`_`')
+* **`AGE`** (written in uppercase)
+* **`Start_Index`** (starts with an uppercase letter and contains '`_`')
+* **`lastNegativeNumber_Index`** (contains '`_`')
 
-At a first look all these rules can seem meaningless and unnecessary, but with time passed and experience gaining you will see the need for norms for writing quality code in order to be able to work more easily and faster in a team. You will understand that the work with a code, which is written without complying with any rules for quality code, is extremely annoying.
+At a first look all these rules can seem meaningless and unnecessary, but with time passed and experience gaining you will see the need for **conventions for writing quality code** in order to be able to work more easily and faster in a team. You will understand that the work with a code, which is written without complying with any rules for code quality, is annoying.