[snmp__if_combined] Reindent

plugins/snmp/snmp__if_combined

@@ -8,22 +8,26 @@ snmp__if_combined - SNMP card plugin to monitor the network interfaces of any ne
 =head1 APPLICABLE SYSTEMS
 
 Any SNMP capable networked computer equipment.  Using a command such
-as "munin-node-configure --snmp switch.langfeldt.net --snmpversion 2c
---snmpcommunity public | sh -x" should auto-detect all applicable
-interfaces.  On a typical switch you will get one plugin pr. ethernet
-port.  On a router you might get one plugin per VLAN interface.
+as
+
+    munin-node-configure --snmp switch.langfeldt.net --snmpversion 2c --snmpcommunity public | sh -x
+
+should auto-detect all applicable interfaces.  On a typical switch you will get
+one plugin pr. ethernet port.  On a router you might get one plugin per VLAN
+interface.
 
 =head2 NOTABLE DIFFERENCE WITH SNMP__IF_MULTI
 
-The smnp__if_multi plugin records data in _bytes_ per second, and shows
-them as bps by using CDEFs when graphing. This plugin performs the
-multiplication upon reporting the value, and therefore doesn't have a
-CDEF in the graphing path.
+The `smnp__if_multi` plugin records data in _bytes_ per second, and shows them
+as bps by using CDEFs when graphing. This plugin performs the multiplication
+upon reporting the value, and therefore doesn't have a CDEF in the graphing
+path.
 
-This is important when migration from snmp__if_multi, for at least two aspects:
+This is important when migration from `snmp__if_multi`, for at least two
+aspects:
 
 - Reusing RRDs: it is not possible to just rename the old RRD files from
-  smnp__if_multi, as historical data will be graphed as 8 times smaller than in
+`smnp__if_multi`, as historical data will be graphed as 8 times smaller than in
 reality. The stored values would need to be adjusted.
 - Data loaning: borrowing graphs no longer need to include a CDEF to convert
 bytes to bits. Conversely, they do now need a CDEF to convert bits to bytes.
@@ -70,9 +74,9 @@ would normally be for VPNs.  A minor horde of different interface types
 are supposted, please see IANAifType-MIB (on your system or find with
 Google) for a full list.
 
-The stackedRoot option determines whether the root summary graph shows the traffic
-on each interface separately, or stacks them on top of one another to show the
-total traffic through the device.
+The `stackedRoot` option determines whether the root summary graph shows the
+traffic on each interface separately, or stacks them on top of one another to
+show the total traffic through the device.
 
 =head1 INTERPRETATION
 
@@ -85,7 +89,7 @@ two additional series are calculated to show the total usage of the device.
 Those series are useful for loaning into higher-level summary graphs (but see
 BUGS below).
 
-Sub-graphs are created, one per interface, akin to snmp__if_multi
+Sub-graphs are created, one per interface, akin to `snmp__if_multi`
 plugin.
 
 =head1 MIB INFORMATION
@@ -126,7 +130,7 @@ Should support indexing by
 
 When using the `stackedRoot` option, the total lines (`send_bits` and
 `recv_bits`) may sometimes jump to nonsensical values. This is a bug shared with
-the original snmp__if_multi.
+the original `snmp__if_multi`.
 
 This seems to be due to the way those series are calculated, by summing the
 current values of the other counters. The first issue is that of summing 64-bit
@@ -511,8 +515,8 @@ sub do_collect {
 
     $snmpinfo = $session->get_hash(
         -baseoid => $ifOIDBase,
-	-cols    =>
-	{ 2  => 'ifDescr',
+        -cols    => {
+            2  => 'ifDescr',
             # Type: See above
             3  => 'ifType',
             5  => 'ifSpeed',
@@ -531,8 +535,8 @@ sub do_collect {
     # ifXEntry - SNMP v2 and up only - on some devices
     $snmpinfoX = $session->get_hash(
         -baseoid => $ifv2OIDBase,
-	-cols    =>
-	{ 6  => 'ifHCInOctets',
+        -cols    => {
+            6  => 'ifHCInOctets',
             10 => 'ifHCOutOctets',
             15 => 'ifHighSpeed',
             18 => 'ifAlias',