diff --git a/content/post/common-test-for-elixir.md b/content/post/common-test-for-elixir.md
index d299f64..ec596bb 100644
--- a/content/post/common-test-for-elixir.md
+++ b/content/post/common-test-for-elixir.md
@@ -103,12 +103,12 @@ this is still used in 2019), some CSS files, some HTML and other.
 
 Just check [this out](/common-test-example/simple/index.html). This is example report
 generated by the Common Test. As you can see it contains a lot of information in
-quite readable format. Not only it contains informations about current run, but
+quite readable format. Not only it contains information about current run, but
 all previous runs as well, which is really handy when tracking regressions.
 
-But can we store even more informations there? Yes, as CT includes simple
-logging facility it is completely possible to log your own informations during
-tests, for example, lets modify our test to log some informations:
+But can we store even more information there? Yes, as CT includes simple
+logging facility it is completely possible to log your own information during
+tests, for example, lets modify our test to log some information:
 
 ```erlang
 test_function_name(_Config) ->
@@ -116,7 +116,7 @@ test_function_name(_Config) ->
     2 = 1 + 1.
 ```
 
-Now when we run tests again, then we will see more informations (even coloured)
+Now when we run tests again, then we will see more information (even coloured)
 in [our test log](/common-test-example/log/ct_run.ct@NiunioBook.2019-07-16_11.03.21/common-test-example.log.logs/run.2019-07-16_11.03.22/example_suite.test_function_name.html):
 
 ![Common Test log "Example message" on green background](/img/common-test/log.png)
diff --git a/content/post/log-all-the-things.md b/content/post/log-all-the-things.md
index 49f0ace..85d1874 100644
--- a/content/post/log-all-the-things.md
+++ b/content/post/log-all-the-things.md
@@ -308,7 +308,7 @@ Logger.error(
 )
 ```
 
-As we can see there, the report contains informations like:
+As we can see there, the report contains information like:
 
 - `:label` - that describes type of the event
 - `:report` - content of the "main" event
diff --git a/content/post/who-watches-watchmen-i.md b/content/post/who-watches-watchmen-i.md
index 05704e1..063acee 100644
--- a/content/post/who-watches-watchmen-i.md
+++ b/content/post/who-watches-watchmen-i.md
@@ -238,13 +238,13 @@ Two possible solutions for this problem are:
 
 systemd supports the second approach via [`sd_notify`][sd_notify]. The approach
 there is simple - we have `NOTIFY_SOCKET` environment variable that contain path
-to the Unix datagram socket, that we can use to send informations about state of
+to the Unix datagram socket, that we can use to send information about state of
 our application. This socket accept set of different messages, but right now,
 for our purposes, we will focus only on few of them:
 
 - `READY=1` - marks our service as ready, aka it is ready to do its work (for
   example accept incoming HTTP connections in our example). It need to be sent
-  withing given timespan after start of the VM, otherwise the process will be
+  within given timespan after start of the VM, otherwise the process will be
   killed and possibly restarted
 - `STATUS=name` - sets status of our application that can be checked via
   `systemctl status hello.service`, this allows us to have better insight into