Use single backticks for inline code unless the code itself contains …

…backticks

CONTRIBUTING.md

@@ -14,9 +14,9 @@ Your pull requests will then be reviewed and discussed.
 
 OpenStreetMap Carto uses a YAML file for defining layers. Some of the rationale is outlined in [a GitHub issue](https://github.com/gravitystorm/openstreetmap-carto/issues/711). Editing multi-line SQL statements in a YAML file is much friendlier than editing escaped SQL in a JSON file.
 
-This requires a preprocessing step to convert the YAML to JSON. A script is provided at ``scripts/yaml2mml.py``, which depends on PyYAML, available through ``pip install pyyaml`` or packaged on Ubuntu as ``python-yaml``.
+This requires a preprocessing step to convert the YAML to JSON. A script is provided at `scripts/yaml2mml.py`, which depends on PyYAML, available through `pip install pyyaml` or packaged on Ubuntu as `python-yaml`.
 
-After editing the YAML file, run ``./scripts/yaml2mml.py < project.yaml > project.mml && touch project.mml`` to update the file and force TileMill to reload it.
+After editing the YAML file, run `./scripts/yaml2mml.py < project.yaml > project.mml && touch project.mml` to update the file and force TileMill to reload it.
 
 When committing changes, add both the `project.yaml` and `project.mml` files to the commit. One of the big advantages of this system is that to resolve any layer merge conflicts, they only need to be resolved in the YAML file where they are easier to handle, then the JSON file can be regenerated, while at the same time the styles work with Tilemill out-of-the-box without needing to run the `yaml2mml` script.
 
@@ -62,10 +62,10 @@ Because SQL within JSON or YAML will not generally be syntax highlighted, indent
 
 * SQL keywords in caps, as in PostgreSQL documentation
 * Two space indents. No tabs.
-* Start with ``(SELECT`` and start the columns on the next line.
+* Start with `(SELECT` and start the columns on the next line.
 * Two indents for columns, to bring them to the same indent level as later clause contents
-* Add indentation after ``SELECT``s until the end of the sub-select.
-* Add indentation for contents of ``FROM``, ``WHERE``, ``ORDER BY`` and other clauses
+* Add indentation after `SELECT`s until the end of the sub-select.
+* Add indentation for contents of `FROM`, `WHERE`, `ORDER BY` and other clauses
 * Put content with WHERE, etc if it's short
 * Add indentation if necessary for complex function calls, WHERE parenthesis, and CASE statements
 * One space before and after = etc

INSTALL.md

@@ -1,6 +1,6 @@
 # Installation
 
-You need OpenStreetMap data loaded into a PostGIS database (see below for [dependencies](https://github.com/gravitystorm/openstreetmap-carto#dependencies)). These stylesheets currently work only with the osm2pgsql defaults (i.e. database name is ``gis``, table names are ``planet_osm_point``, etc).
+You need OpenStreetMap data loaded into a PostGIS database (see below for [dependencies](https://github.com/gravitystorm/openstreetmap-carto#dependencies)). These stylesheets currently work only with the osm2pgsql defaults (i.e. database name is `gis`, table names are `planet_osm_point`, etc).
 
 It's probably easiest to grab an PBF of OSM data from [Mapzen](https://mapzen.com/metro-extracts/) or [geofabrik](http://download.geofabrik.de/). Once you've set up your PostGIS database, import with osm2pgsql:
 
@@ -24,15 +24,15 @@ To download the shapefiles you can run the following script from this directory.
 
 You can also download them manually at the following paths:
 
-* [``simplified-land-polygons.shp``](http://data.openstreetmapdata.com/simplified-land-polygons-complete-3857.zip) (updated daily)
-* [``land-polygon.shp``](http://data.openstreetmapdata.com/land-polygons-split-3857.zip) (updated daily)
-* [``builtup_area.shp``](http://planet.openstreetmap.org/historical-shapefiles/world_boundaries-spherical.tgz)
-* [``ne_110m_admin_0_boundary_lines_land.shp``](http://www.naturalearthdata.com/http//www.naturalearthdata.com/download/110m/cultural/ne_110m_admin_0_boundary_lines_land.zip)
-* [``ne_10m_populated_places_fixed.shp``](http://www.naturalearthdata.com/http//www.naturalearthdata.com/download/10m/cultural/ne_10m_populated_places.zip) (and see [below](#populated-places-shapefile))
+* [`simplified-land-polygons.shp`](http://data.openstreetmapdata.com/simplified-land-polygons-complete-3857.zip) (updated daily)
+* [`land-polygon.shp`](http://data.openstreetmapdata.com/land-polygons-split-3857.zip) (updated daily)
+* [`builtup_area.shp`](http://planet.openstreetmap.org/historical-shapefiles/world_boundaries-spherical.tgz)
+* [`ne_110m_admin_0_boundary_lines_land.shp`](http://www.naturalearthdata.com/http//www.naturalearthdata.com/download/110m/cultural/ne_110m_admin_0_boundary_lines_land.zip)
+* [`ne_10m_populated_places_fixed.shp`](http://www.naturalearthdata.com/http//www.naturalearthdata.com/download/10m/cultural/ne_10m_populated_places.zip) (and see [below](#populated-places-shapefile))
 
 The repeated www.naturalearthdata.com in the Natural Earth shapefiles is correct.
 
-Put these shapefiles at ``path/to/openstreetmap-carto/data``.
+Put these shapefiles at `path/to/openstreetmap-carto/data`.
 
 ### Populated places shapefile
 
@@ -51,21 +51,21 @@ The stylesheet depends on a number of openly licensed fonts for support of all t
 If a font is missing, it will skip to the next available font which contains those characters. If you are not concerned with a particular language, you do not need its fonts. DejaVu Sans and Unifont are the two required fonts, and included on most systems.
 
 ### Global
-* DejaVu Sans, for most languages (``ttf-dejavu``)
-* Droid Sans Fallback, as a reasonable fallback (``fonts-droid``)
-* Unifont, as a last resort fallback (``ttf-unifont``)
+* DejaVu Sans, for most languages (`ttf-dejavu`)
+* Droid Sans Fallback, as a reasonable fallback (`fonts-droid`)
+* Unifont, as a last resort fallback (`ttf-unifont`)
 
 ### Southeast Asia
-* Arundina Sans, for Thai (``fonts-sipa-arundina``)
-* Padauk, for Burmese (``fonts-sil-padauk``)
-* Khmer OS Metal Chrieng Regular, for Khmer (``fonts-khmeros``)
+* Arundina Sans, for Thai (`fonts-sipa-arundina`)
+* Padauk, for Burmese (`fonts-sil-padauk`)
+* Khmer OS Metal Chrieng Regular, for Khmer (`fonts-khmeros`)
 
 ### South Asia
 
-* Mukti Narrow, for Bangali (``ttf-indic-fonts-core``)
-* Gargi Medium, for Devanagari (``ttf-indic-fonts-core``)
-* TSCu_Paranar, for Tamil (``ttf-tamil-fonts``)
-* Mallige, for Kannada (``ttf-indic-fonts-core`` for normal and bold and ``ttf-kannada-fonts`` for oblique) *The filename uses "Malige" but the font name uses "Mallige"*
+* Mukti Narrow, for Bangali (`ttf-indic-fonts-core`)
+* Gargi Medium, for Devanagari (`ttf-indic-fonts-core`)
+* TSCu_Paranar, for Tamil (`ttf-tamil-fonts`)
+* Mallige, for Kannada (`ttf-indic-fonts-core` for normal and bold and `ttf-kannada-fonts` for oblique) *The filename uses "Malige" but the font name uses "Mallige"*
 
 On Ubuntu you can install all the fonts with
 
@@ -92,4 +92,4 @@ If you aren't using TileMill, you can compile the CartoCSS stylesheets into Mapn
 * curl, unzip for downloading and decompressing files
 * shapeindex (a companion utility to Mapnik found in the mapnik-utils package) for indexing downloaded shapefiles
 
-* [PyYAML] (http://pyyaml.org/wiki/PyYAML) if editing the MML (layer definition) file (packaged as ``python-yaml`` on Ubuntu, or installed with ``pip install pyyaml``)
+* [PyYAML](http://pyyaml.org/wiki/PyYAML) if editing the MML (layer definition) file (packaged as `python-yaml` on Ubuntu, or installed with `pip install pyyaml`)