Remove double quote escapes from readme

ESRO/README.md

@@ -33,7 +33,7 @@ For these properties on a Character or Handout object, the `get` function is asy
 #### Functions of Wrapped Objects
 In addition to direct property access, there are some functions available to wrapped objects. The list of available functions includes *all* functions that are normally available to the Roll20 objects (`get`, `set`, `remove`, etc.) even if some (`get` and `set`, specifically) are redundant.
 
-**toString(minimal)**: the `toString` function has been redefined for wrapped objects. Instead of simply outputting \"[object Object]\", it will attempt to produce the JSON data for the object. In corner cases where that is not possible, or if you provide `true` as a parameter to the function, it will return \"[object Roll20Object -Abc_123]\" (using the object's actual `id` instead of `-Abc_123`). In corner cases where it is not possible to include the object's id, the return value will simply be \"[object Roll20Object]\", which at least is still more descriptive than the standard `toString`.
+**toString(minimal)**: the `toString` function has been redefined for wrapped objects. Instead of simply outputting "[object Object]", it will attempt to produce the JSON data for the object. In corner cases where that is not possible, or if you provide `true` as a parameter to the function, it will return "[object Roll20Object -Abc_123]" (using the object's actual `id` instead of `-Abc_123`). In corner cases where it is not possible to include the object's id, the return value will simply be "[object Roll20Object]", which at least is still more descriptive than the standard `toString`.
 
 **unwrap()**: the `unwrap` function is available for all wrapped objects to gain access to the original, unwrapped version of the object. This should not be needed under most circumstances, but it is required for `toFront` and `toBack` if you are not overwriting them despite using wrapped objects in your script.