Fix typos in a test and in a doc (#13799)

lib/elixir/pages/anti-patterns/macro-anti-patterns.md

@@ -67,7 +67,7 @@ To address this anti-pattern, a macro can expand literals within the context the
   end
 ```
 
-In the example above, since `mod` is used only within the `call/2` function, we prematuraly expand module reference as if it was inside the `call/2` function. Now `MyApp.Authentication` is only a runtime dependency of `MyApp`, no longer a compile-time one.
+In the example above, since `mod` is used only within the `call/2` function, we prematurely expand module reference as if it was inside the `call/2` function. Now `MyApp.Authentication` is only a runtime dependency of `MyApp`, no longer a compile-time one.
 
 Note, however, the above must only be done if your macros do not attempt to invoke any function, access any struct, or any other metadata of the module at compile-time. If you interact with the module given to a macro anywhere outside of definition of a function, then you effectively have a compile-time dependency. And, even though you generally want to avoid them, it is not always possible.
 

lib/iex/test/iex/pry_test.exs

@@ -195,7 +195,7 @@ defmodule IEx.PryTest do
       Macro.to_string({:__block__, meta, tail})
     end
 
-    test "one expresion, one line" do
+    test "one expression, one line" do
       assert annotate_quoted("""
              x = 123
              y = 456