Update diktat-coding-convention.md

### What's done:
Updates to code-style

info/guide/diktat-coding-convention.md

@@ -69,7 +69,7 @@ Note: The source file encoding format (including comments) must be UTF-8 only. T
 
 <!-- =============================================================================== -->
 ### <a name="c1.1"></a> 1.1 Identifier names
-### <a name="r1.1.1"></a> 1.1.1: Identifiers naming conventions
+### <a name="r1.1.1"></a> Rule 1.1.1: Identifiers naming conventions
 
 For identifiers, use the following naming conventions:
 1.	All identifiers should use only ASCII letters or digits, and the names should match regular expressions `\w{2,64}`.
@@ -130,7 +130,7 @@ Note that prefixing can also negatively affect the style and the auto-generation
 
 <!-- =============================================================================== -->
 ### <a name="c1.2"></a> 1.2 Packages names
-### <a name="r1.2.1"></a> Rule 1.2.1: Package names dots
+### <a name="r1.2.1"></a> Rule 1.2.1: Format of package names 
 Package names are in lower case and separated by dots. Code developed within your company should start with `your.company.domain.` Numbers are permitted in package names.
 Each file should have a `package` directive.
 Package names are all written in lowercase, and consecutive words are concatenated together (no underscores). Package names should contain both the product and module names, and the department (or team) name to prevent conflicts with other teams.  Numbers are not permitted. For example: `org.apache.commons.lang3`, `xxx.yyy.v2`.
@@ -2103,4 +2103,4 @@ interface I {
 object O: I {
     override fun foo() {}
 }
-```
+```