aboutsummaryrefslogtreecommitdiffstats
diff options
context:
space:
mode:
authorAndrew Hendrie <hendrieandrew91@gmail.com>2015-03-09 20:20:06 -0400
committerAndrew Hendrie <hendrieandrew91@gmail.com>2015-03-09 20:20:06 -0400
commit3f0b7b41e11d7551a359d6cae9e547487baf9351 (patch)
tree2afb4d5141646596187487199d5d071097aa1b1a
parent761b5541b645bc1863b71008d6856eb1d2d46806 (diff)
downloadrails-3f0b7b41e11d7551a359d6cae9e547487baf9351.tar.gz
rails-3f0b7b41e11d7551a359d6cae9e547487baf9351.tar.bz2
rails-3f0b7b41e11d7551a359d6cae9e547487baf9351.zip
Changed 'blank space' to 'blank line'
Line 85 stated that fixtures are typically separated by a blank space. I changed the wording to blank line because blank space could be misinterpreted as a non-breaking space character when in reality, each fixture record (in YAML) is separated by a blank line.
-rw-r--r--guides/source/testing.md2
1 files changed, 1 insertions, 1 deletions
diff --git a/guides/source/testing.md b/guides/source/testing.md
index cb3bd68fbe..b508969f30 100644
--- a/guides/source/testing.md
+++ b/guides/source/testing.md
@@ -82,7 +82,7 @@ steve:
profession: guy with keyboard
```
-Each fixture is given a name followed by an indented list of colon-separated key/value pairs. Records are typically separated by a blank space. You can place comments in a fixture file by using the # character in the first column.
+Each fixture is given a name followed by an indented list of colon-separated key/value pairs. Records are typically separated by a blank line. You can place comments in a fixture file by using the # character in the first column.
If you are working with [associations](/association_basics.html), you can simply
define a reference node between two different fixtures. Here's an example with