diff options
author | Pieter van de Bruggen <pvande@gmail.com> | 2011-02-03 10:59:30 -0800 |
---|---|---|
committer | Pieter van de Bruggen <pvande@gmail.com> | 2011-02-03 10:59:30 -0800 |
commit | f75ffbf0a90e6ccecb11df58cdb4cc400ac2919d (patch) | |
tree | ad169d9f6026b511b26dae79ad403a55a82bf58b | |
parent | 572b582e7c6ac0650785de930efbfe9633f7818d (diff) | |
download | mustache-spec-f75ffbf0a90e6ccecb11df58cdb4cc400ac2919d.tar.gz |
Fixing a markup error in the docs.
-rw-r--r-- | README.md | 2 | ||||
-rw-r--r-- | TESTING.md | 2 |
2 files changed, 2 insertions, 2 deletions
@@ -40,6 +40,6 @@ build`. It is also worth noting that some specifications (notably, the lambda module) rely on YAML "tags" to denote special types of data (e.g. source code). Since -JSON offers no way to denote this, a special key ("__tag__") is injected with +JSON offers no way to denote this, a special key ("`__tag__`") is injected with the name of the tag as its value. See `TESTING.md` for more information about handling tagged data. @@ -32,7 +32,7 @@ In general, the process for each `.yml` file is as follows: request. * The JSON version of the spec represents these tagged values as a hash - with a '__tag__' key of 'code'. + with a '`__tag__`' key of 'code'. 3. Render the template (stored in the 'template' key) with the given 'data' hash. |