summaryrefslogtreecommitdiff
diff options
context:
space:
mode:
authorbrent s <r00t@square-r00t.net>2017-11-27 01:18:30 -0500
committerbrent s <r00t@square-r00t.net>2017-11-27 01:18:30 -0500
commite2cb61716be17086cef27c457953ce09ba56fa2d (patch)
treecf36213b21ed7ebe1d030c5ea29d7a0f48d87e97
parent259330f6b2165671a6d91b54a2f68071f9db5528 (diff)
downloadRelSpec-e2cb61716be17086cef27c457953ce09ba56fa2d.tar.xz
fixed "is" => "are"
-rw-r--r--README.txt2
1 files changed, 1 insertions, 1 deletions
diff --git a/README.txt b/README.txt
index 8f50e9b..5cd113e 100644
--- a/README.txt
+++ b/README.txt
@@ -24,7 +24,7 @@ Many software authors ("upstream") rely on packagers ("downstream") - that is,
in various community-driven methods of distribution (GNU/Linux distributions'
repository packagers, BSD's packagers, FreeBSD's Ports maintainers, etc.) and it
is beneficial to these downstream maintainers to be alerted when new versions of
-software is released.
+software are released.
However, not all upstream sources provide the same mechanism for checking this
(spread across mailing lists, front page news, blog posts, etc.) - and sometimes