Permalink
Browse files

Fixing a markup error in the docs.

  • Loading branch information...
1 parent 572b582 commit f75ffbf0a90e6ccecb11df58cdb4cc400ac2919d @pvande pvande committed Feb 3, 2011
Showing with 2 additions and 2 deletions.
  1. +1 −1 README.md
  2. +1 −1 TESTING.md
View
@@ -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.
View
@@ -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.

0 comments on commit f75ffbf

Please sign in to comment.