From 831bd7027b1651916f3577c185d90b3f513b146e Mon Sep 17 00:00:00 2001 From: Ethan Hall Date: Fri, 28 Sep 2018 10:35:08 -0700 Subject: [PATCH] Update README.md --- README.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/README.md b/README.md index fd65056..5f79e89 100644 --- a/README.md +++ b/README.md @@ -14,7 +14,7 @@ Inc[luding] your configuration, one step at a time. But these are only examples. `inc` is intended to be flexible enough for teams to describe what they need, to do. A common use-case is to put complicated build logic behind a single command so no new team member needs to remember this project's specific parameters. ## Install -You can grab the lastest releases from [Github](https://github.com/ethankhall/inc/releases). If you're lazy and just want to run a script do `bash <(curl -s https://raw.githubusercontent.com/ethankhall/inc/master/install.sh) +You can grab the lastest releases from [Github](https://github.com/ethankhall/inc/releases). If you're lazy and just want to run a script do `bash <(curl -s https://raw.githubusercontent.com/ethankhall/inc/master/install.sh)` ## What's Included? While `inc` doesn't come with AA batteries, it comes with the the coin-cell to get you going. There are several commands that will come with `inc`. You're free to use one, some, all or none of them. The default commands are: