diff --git a/README.md b/README.md
index f462dea..4d888a6 100644
--- a/README.md
+++ b/README.md
@@ -46,13 +46,13 @@ The main advantages on using JuNest are:
 
 JuNest follows the [Arch Linux philosophy](https://wiki.archlinux.org/index.php/The_Arch_Way).
 
-How different JuNest is from Docker and Vagrant?
+How different is JuNest from Docker and Vagrant?
 ------------------------------------------------
 Although JuNest sounds similar to a virtualisation/Linux container -like system,
 JuNest differentiate a lot between Docker and Vagrant.
 In fact, the purpose of JuNest is **not** to
 build a complete isolated environment but, conversely, is the ability to run
-programs as they are running natively from the host OS. Almost everything is shared
+programs as they were running natively from the host OS. Almost everything is shared
 between host OS and the JuNest sandbox (kernel, process subtree, network, mounting, etc)
 and only the root filesystem gets isolated
 (as the programs installed in JuNest need to reside elsewhere).
diff --git a/lib/checks/check.sh b/lib/checks/check.sh
index 7f38937..e361913 100755
--- a/lib/checks/check.sh
+++ b/lib/checks/check.sh
@@ -32,7 +32,11 @@ info "Validating JuNest located in ${JUNEST_HOME}..."
 
 info "Initial JuNest setup..."
 echo "Server = ${DEFAULT_MIRROR}" >> /etc/pacman.d/mirrorlist
-pacman --noconfirm -Syyu
+pacman --noconfirm -Syy
+pacman --noconfirm -S archlinux-keyring
+pacman-key --init
+pacman-key --populate archlinux
+pacman --noconfirm -Su
 pacman --noconfirm -S grep coreutils
 pacman --noconfirm -S $(pacman -Sg base-devel | cut -d ' ' -f 2 | grep -v sudo)