Add code tags

Author: aishwarya-sankhla

guides/coding_style/perl/style.md

@@ -1,8 +1,8 @@
 Perl Code Style Guidelines
 
+```perl
 Indentation:
 Tabs should be used to indent all code blocks.  Spaces should never be used to indent code blocks.  Mixing tabs and spaces results in misaligned code blocks for other developers who prefer different indentation settings.
-
 if ($total_hours >= 24) {
 	return 1;
 }
@@ -14,27 +14,41 @@ else {
 		return 0;
 	}
 }
+```
 
+```perl
 Comments:
 There should always be at least 1 space between the # character and the beginning of the comment.  This makes it a little easier to read multi-line comments:
 # Comments are your friend, they help
+```
 
+```perl
 Subroutine & Variable Names:
 Single letter variable names should never be used unless for a loop iterator:
+```
 
+```perl
 Avoid abbreviations:
 my $ip_addr; ->No
 my $ip_address; ->Yes
+```
 
+```perl
 Use underscores to separate words:
 sub get_computer_name {
+```
 
+```perl
 All subroutine names should be entirely lowercase:
 sub update_request_state {
+```
 
+```perl
 All class variables defined at the top of a .pm file should be entirely uppercase:
 our $SOURCE_CONFIGURATION_DIRECTORY = "$TOOLS/Windows";
+```
 
+```perl
 POD Documentation
 All modules and subroutines must contain a POD documentation block describing what it does. POD is "Plain Old Documentation".
 
@@ -54,11 +68,15 @@ Each subroutine should begin with a POD block with the following format:
 sub my_subroutine_name {
 
 }
+```
 
+```perl
 Curly Brackets, Parenthesis:
 There should be a space between every control/loop keyword and the opening parenthesis:
 if ($loop_count <= 10) {
+```
 
+```perl
 If/Else Statements:
 'else' & 'elsif' statements should be on a separate line after the previous closing curly brace:
 if ($end_time < $now) {
@@ -67,3 +85,4 @@ if ($end_time < $now) {
 else {
    ...
 }
+```