summaryrefslogtreecommitdiff
diff options
context:
space:
mode:
authorshotat <shotat@users.noreply.github.com>2016-09-16 03:02:19 +0900
committerJames Fish <james@fishcakez.com>2016-09-15 19:02:19 +0100
commit77ae863bd02ca90496b96854249b8942ac76b8b4 (patch)
tree2fd3236495d9b5de89a3e73edb6759a243d8330b
parent76b355a9d90989987174a87957622ecc372add00 (diff)
downloadelixir-77ae863bd02ca90496b96854249b8942ac76b8b4.tar.gz
fix typo (#5223)
-rw-r--r--lib/ex_unit/lib/ex_unit/assertions.ex6
1 files changed, 3 insertions, 3 deletions
diff --git a/lib/ex_unit/lib/ex_unit/assertions.ex b/lib/ex_unit/lib/ex_unit/assertions.ex
index 94ee9f8f2..729ba7100 100644
--- a/lib/ex_unit/lib/ex_unit/assertions.ex
+++ b/lib/ex_unit/lib/ex_unit/assertions.ex
@@ -47,7 +47,7 @@ defmodule ExUnit.Assertions do
In general, a developer will want to use the general
`assert` macro in tests. This macro introspects your code
- and provide good reporting whenever there is a failure.
+ and provides good reporting whenever there is a failure.
For example, `assert some_fun() == 10` will fail (assuming
`some_fun()` returns 13):
@@ -65,8 +65,8 @@ defmodule ExUnit.Assertions do
@doc """
Asserts its argument is a truthy value.
- `assert` instrospects the underlying expression and provide
- good reporting whenever there is a failure. For example,
+ `assert` introspects the underlying expression and provides
+ good reporting whenever there is a failure. For example,
if the expression uses the comparison operator, the message
will show the values of the two sides. The assertion