Style fixes in documentation's example code

diff --git a/README.markdown b/README.markdown
index 5132d258210f85ed76c9d9af860f2a03d278551e..9a7f5e009a64874165a5e0eaf4ae851b626fef71 100644 (file)
--- a/README.markdown
+++ b/README.markdown
@@ -136,7 +136,7 @@ Rules are persisted automatically between reboots, although there are known issu
   
   ~~~puppet
   resources { 'firewall':
-    purge => true
+    purge => true,
   }
   ~~~
 
@@ -144,7 +144,7 @@ Rules are persisted automatically between reboots, although there are known issu
 
   ~~~puppet
   resources { 'firewallchain':
-    purge => true
+    purge => true,
   }
   ~~~
   
@@ -198,17 +198,17 @@ In iptables, the title of the rule is stored using the comment feature of the un
 Basic accept ICMP request example:
 
 ~~~puppet
-firewall { "000 accept all icmp requests":
-  proto  => "icmp",
-  action => "accept",
+firewall { '000 accept all icmp requests':
+  proto  => 'icmp',
+  action => 'accept',
 }
 ~~~
 
 Drop all:
 
 ~~~puppet
-firewall { "999 drop all other requests":
-  action => "drop",
+firewall { '999 drop all other requests':
+  action => 'drop',
 }
 ~~~
 
@@ -217,7 +217,7 @@ firewall { "999 drop all other requests":
 IPv6 rules can be specified using the _ip6tables_ provider:
 
 ~~~puppet
-firewall { "006 Allow inbound SSH (v6)":
+firewall { '006 Allow inbound SSH (v6)':
   port     => 22,
   proto    => tcp,
   action   => accept,
@@ -279,7 +279,7 @@ You can apply firewall rules to specific nodes. Usually, you will want to put th
 ~~~puppet
 node 'some.node.com' {
   firewall { '111 open port 111':
-    dport => 111
+    dport => 111,
   }
 }
 ~~~
@@ -291,7 +291,7 @@ firewall { '100 snat for network foo2':
   chain    => 'POSTROUTING',
   jump     => 'MASQUERADE',
   proto    => 'all',
-  outiface => "eth0",
+  outiface => 'eth0',
   source   => '10.1.2.0/24',
   table    => 'nat',
 }
@@ -812,7 +812,7 @@ firewallchain { 'INPUT:filter:IPv4':
 
 ~~~puppet
 resources { 'firewallchain':
-  purge => true
+  purge => true,
 }
 ~~~