commit: 91eb2fe1a0891306ac1924a312200126edd6d8e9
parent dc045285a3367aba32c4dd274e2f9d6010b42457
Author: Drew DeVault <sir@cmpwn.com>
Date: Wed, 10 Feb 2021 07:54:17 -0500
Fix typo
Diffstat:
1 file changed, 3 insertions(+), 3 deletions(-)
diff --git a/content/blog/How-to-make-your-downstreams-happy.md b/content/blog/How-to-make-your-downstreams-happy.md
@@ -37,9 +37,9 @@ be using [git tags][0] for your releases — consider putting a changelog
into your annotated tags (git tag -a). If you have [good commit discipline][1]
in your project, then you can easily use [git shortlog][2] to generate such a
changelog from your commit messages. This helps us understand what we can expect
-when upgrading, which helps incentive us to upgrade in the first place. In [How
-to fuck up software releases][3], I wrote about my [semver][4] tool, which you
-may find helpful in automating this process. It can also help you avoid
+when upgrading, which helps incentivize us to upgrade in the first place. In
+[How to fuck up software releases][3], I wrote about my [semver][4] tool, which
+you may find helpful in automating this process. It can also help you avoid
forgetting to do things like update the version number somewhere in the code.
[0]: https://git-scm.com/docs/git-tag
