From bb7bb3487029c90502fc8a13cf83eda8c1254c32 Mon Sep 17 00:00:00 2001 From: Andy Lulham Date: Tue, 17 Sep 2019 12:18:07 +0100 Subject: [PATCH] Fix a couple of minor README typos --- README.md | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) diff --git a/README.md b/README.md index 890037b..6731b1c 100644 --- a/README.md +++ b/README.md @@ -12,7 +12,7 @@ I love using `Makefile` for one-off **tasks** in projects. -The problem with doing this is that you can't use familiar bash–isms when doing so, as **GNU Make** doesn't use the familiar **Bash** syntax, nor does it allow for simple ad–hoc use of abritrary scripting languages (e.g. **Python**). +The problem with doing this is that you can't use familiar bash–isms when doing so, as **GNU Make** doesn't use the familiar **Bash** syntax, nor does it allow for simple ad–hoc use of arbitrary scripting languages (e.g. **Python**). This project seeks to bridge all of these worlds into a single entrypoint — ideal for cross–language repositories. @@ -28,7 +28,7 @@ This project seeks to bridge all of these worlds into a single entrypoint — i - A `Bakefile`, which looks and feels like the good parts of a `Makefile`. - Except, you can write real bash code! -- Environment variables are explicitly passed or whitelisted (allowed), not inherinted from the parent shell. +- Environment variables are explicitly passed or whitelisted (allowed), not inherited from the parent shell. - Unlike `Makefile`, either tabs or 4 spaces can be used. - Tasks can be run safely and reliably. Rest assured that scripts are executed from the project root (e.g. location of the `Bakefile`). - See [advanced example](https://github.com/kennethreitz/bake#advanced-usage-sample) for further, juicy, details.