Updated RFC: Raster bands interpretation specification (markdown)

RFC:-Raster-bands-interpretation-specification.md

@@ -10,36 +10,45 @@ This page is an attempt to standardize bands extraction and interpretation in a
 The band parameter could have the following values:
 
  - `rgb[:<r>,<g>,<b>]`
-   Where <r>, <g> and <b> are integer representing 1-based band indexes.
+
+   Where `<r>`, `<g>` and `<b>` are integer representing 1-based band indexes.
  
  - `rgb`
+
    Same as `rgb:1,2,3`
 
  - `rgba[:<r>,<g>,<b>,<a>]`
-   Where <r>, <g>, <b> and <a> are integer representing 1-based band indexes.
+
+    Where `<r>`, `<g>`, `<b>` and `<a>` are integer representing 1-based band indexes.
    
  - `rgba`
+
     Same as `rgba:1,2,3,4`
 
  - `grayscale[:<n>]`
-   Where <n> is an integer representing 1-based band indexes.
+   Where `<n>` is an integer representing 1-based band indexes.
 
  - 'grayscale'
+
    Same as `grayscale:1`
 
  - `data[:<n>]`
-   Where <n> is an integer representing 1-based band indexes.
+
+   Where `<n>` is an integer representing 1-based band indexes.
 
  - `<n>`
-   Same as data:<n>
+
+   Same as `data:<n>`
    This is for backward compatibility with the GDAL plugin
 
  - `auto`
+
    The default value, if band parameter is omitted, enables guess based on input raster:
    - If the input has 3 bands, `rgb` assumed
    - If the input has 4 bands, `rgba` assumed
    - If the input has 1 band, `grayscale` assumed
 
  - `-1`
+
    Same as `auto`
    This is for backward compatibility with the GDAL plugin