aboutsummaryrefslogtreecommitdiffstats
path: root/guides
diff options
context:
space:
mode:
authorShailesh Kalamkar <shailesh.kalamkar@gmail.com>2019-03-09 12:13:28 +0530
committerShailesh Kalamkar <shailesh.kalamkar@gmail.com>2019-03-09 12:15:00 +0530
commit70192cec42c0133791010537fd602089c81986a4 (patch)
tree6b55b39195a0fb90436d81701761806f6a34f03c /guides
parent0771bd3ee891f8eaf822bb47f68f4d0266763728 (diff)
downloadrails-70192cec42c0133791010537fd602089c81986a4.tar.gz
rails-70192cec42c0133791010537fd602089c81986a4.tar.bz2
rails-70192cec42c0133791010537fd602089c81986a4.zip
[ci skip] Minor documentation fixes for consistency
Diffstat (limited to 'guides')
-rw-r--r--guides/source/autoloading_and_reloading_constants.md2
-rw-r--r--guides/source/testing.md2
2 files changed, 2 insertions, 2 deletions
diff --git a/guides/source/autoloading_and_reloading_constants.md b/guides/source/autoloading_and_reloading_constants.md
index b3f923a017..7dfc39e192 100644
--- a/guides/source/autoloading_and_reloading_constants.md
+++ b/guides/source/autoloading_and_reloading_constants.md
@@ -798,7 +798,7 @@ to load a file using the current [loading mechanism](#loading-mechanism), and
keeping track of constants defined in that file as if they were autoloaded to
have them reloaded as needed.
-`require_dependency` is rarely needed, but see a couple of use-cases in
+`require_dependency` is rarely needed, but see a couple of use cases in
[Autoloading and STI](#autoloading-and-sti) and [When Constants aren't
Triggered](#when-constants-aren-t-missed).
diff --git a/guides/source/testing.md b/guides/source/testing.md
index 8f3a7f67c0..93372b5c26 100644
--- a/guides/source/testing.md
+++ b/guides/source/testing.md
@@ -1012,7 +1012,7 @@ Finally we can assert that our response was successful and our new article is re
#### Taking it further
-We were able to successfully test a very small workflow for visiting our blog and creating a new article. If we wanted to take this further we could add tests for commenting, removing articles, or editing comments. Integration tests are a great place to experiment with all kinds of use-cases for our applications.
+We were able to successfully test a very small workflow for visiting our blog and creating a new article. If we wanted to take this further we could add tests for commenting, removing articles, or editing comments. Integration tests are a great place to experiment with all kinds of use cases for our applications.
Functional Tests for Your Controllers