From e5bf1b3e9a7b3f6e34518a87941a976dafc20008 Mon Sep 17 00:00:00 2001
From: 0xflotus <0xflotus@gmail.com>
Date: Fri, 14 Sep 2018 01:37:55 +0200
Subject: [PATCH] updated environment

---
 README.md | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)

diff --git a/README.md b/README.md
index 39e98b1..4d5ea5b 100644
--- a/README.md
+++ b/README.md
@@ -65,7 +65,7 @@ For example, if you're using Beanstalk/Staker:
 Using a queueing system which doesn't require that your full application be
 loaded is preferable, because the clock process can keep a tiny memory
 footprint.  If you're using DJ or Resque, however, you can go ahead and load
-your full application enviroment, and use per-event blocks to call DJ or Resque
+your full application environment, and use per-event blocks to call DJ or Resque
 enqueue methods.  For example, with DJ/Rails:
 
     require 'config/boot'