highlight methods name

Author: anishmanandhar

docs/general-guidelines.md

@@ -114,7 +114,7 @@ title: General Coding Standards
     Good function names: **getPersonList, fetchUsers, getCurrentUser, removeTodoItems, initialize, clear, flush, activate, isActive(), shouldNotify()**
     Bad function names are those that isn't meaningful to the task it does.
 
-* A function should do one thing and should be named accordingly. SRP(Single Responsibility Principle) also applies here. If you have broken down the function following SRP then there won't be a function such as: getUserByIdAndActivateItAndLogin, checkPeopleAndArchiveThem.
+  * A function should do one thing and should be named accordingly. **SRP(Single Responsibility Principle)** also applies here. If you have broken down the function following SRP then there won't be a function such as: **getUserByIdAndActivateItAndLogin**, **checkPeopleAndArchiveThem** (bad practice).
 
 * All the releases should be properly tagged in git.
 

docusaurus.config.js

@@ -22,7 +22,7 @@ module.exports = {
         },
         {to: 'blog', label: 'Blog', position: 'left'},
         {
-          href: 'https://github.com/facebook/docusaurus',
+          href: 'https://github.com/leapfrogtechnology/coding-guidelines',
           label: 'GitHub',
           position: 'right',
         },
@@ -70,7 +70,7 @@ module.exports = {
             },
             {
               label: 'GitHub',
-              href: 'https://github.com/facebook/docusaurus',
+              href: 'https://github.com/leapfrogtechnology/coding-guidelines',
             },
           ],
         },