From c4b02b12a4ddb861b44ecc1392e8f45d84cfe7cb Mon Sep 17 00:00:00 2001 From: Bradly Feeley Date: Tue, 11 Oct 2016 21:41:12 -0700 Subject: [PATCH] Fixing misspelling of tooling --- README.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/README.md b/README.md index 44cb9f0..ca39217 100644 --- a/README.md +++ b/README.md @@ -417,7 +417,7 @@ There are several approaches to deploying infrastructure with AWS, from the cons The first way most people experiment with AWS is via its web interface, the AWS Console. But using the Console is a highly manual process, and often works against automation or flexibility. -So if you’re not going to manage your AWS configurations manually, what should you do? Sadly, there are no simple, universal answers — each approach has pros and cons, and the approaches taken by different companies vary widely, and include directly using APIs (and building toolign on top yourself), using command-line tools, and using third-party tools and services. +So if you’re not going to manage your AWS configurations manually, what should you do? Sadly, there are no simple, universal answers — each approach has pros and cons, and the approaches taken by different companies vary widely, and include directly using APIs (and building tooling on top yourself), using command-line tools, and using third-party tools and services. ### AWS Console