diff --git a/docs/configuration.md b/docs/configuration.md
index 7b50aba33..57133e666 100644
--- a/docs/configuration.md
+++ b/docs/configuration.md
@@ -302,7 +302,7 @@ The config file is in the [toml format](https://github.com/toml-lang/toml) and h
 
     ```toml
     [metric]
-    service = “statsd”
+    service = "statsd"
     ```
 
 #### Metric Host
@@ -319,7 +319,7 @@ The config file is in the [toml format](https://github.com/toml-lang/toml) and h
 #### Metric Poll Interval
 
 * Description: Rate at which runtime metrics (such as open file handles and memory usage) are collected.
-* Flag: `metric.poll-interval=”0m15s”`
+* Flag: `metric.poll-interval="0m15s"`
 * Env: `PILOSA_METRIC_POLL_INTERVAL=0m15s`
 * Config:
 
diff --git a/docs/examples.md b/docs/examples.md
index c7476a722..eae05ab76 100644
--- a/docs/examples.md
+++ b/docs/examples.md
@@ -81,7 +81,7 @@ lfm := pdk.LinearFloatMapper{
 }
 ```
 
-`Min` and `Max` define the linear function, and `Res` determines the maximum allowed value for the output row ID - we chose these values to produce a “round to nearest integer” behavior. Other predefined mappers have their own specific parameters, usually two or three.
+`Min` and `Max` define the linear function, and `Res` determines the maximum allowed value for the output row ID - we chose these values to produce a "round to nearest integer" behavior. Other predefined mappers have their own specific parameters, usually two or three.
 
 This mapper function is the core operation, but we need a few other pieces to define the overall process, which is encapsulated in the ColumnMapper object. This object defines which field(s) of the input data source to use (`Fields`), how to parse them (`Parsers`), what mapping to use (`Mapper`), and the name of the field to use (`Field`). <!-- TODO update so this makes sense -->
 ```go