Clarify meaning of GPL/AGPL

Signed-off-by: Benjamin Lowry <ben@ben.gmbh>

1 files changed, 8 insertions, 6 deletions

diff --git a/license.md b/license.md
index 518c111..f3e2851 100644
--- a/license.md
+++ b/license.md
@@ -18,18 +18,20 @@ which to use, we can offer some suggestions.
 ## I want others to share their improvements with me.
 
 The Free Software Foundation publishes the GNU General Public License for this
-purpose.  In short, it requires anyone who modifies or reuses your code to
-publish their changes or the software they incorporated it into under the same
-license terms.  Version 3 also requires hardware manufacturers to allow users to
-install their modifications onto devices which use GPLv3 licensed software.
+purpose. In short, it requires anyone who publishes modified versions of your
+code or software that uses it to publish their changes or the software they
+incorporated it into under the same license terms. Version 3 also requires
+hardware manufacturers to allow users to install their modifications onto
+devices which use GPLv3 licensed software.
 
 [GPLv3 information](https://www.gnu.org/licenses/gpl-3.0.en.html) —
 [GPLv3 plain text](https://www.gnu.org/licenses/gpl-3.0.txt)
 
 Authors publishing software which is useful over a network — databases,
 web applications, and so on — should consider the "Affero" General Public
-License, or AGPL, as well. SourceHut itself is distributed with the AGPLv3
-license.
+License, or AGPL, as well. The AGPL is similar to the GPL, but its terms also apply
+when your software is used to provide a service over a network. Sourcehut itself is
+distributed with the AGPLv3 license.
 
 [AGPLv3 information](https://www.gnu.org/licenses/agpl-3.0.html)
 — [AGPLv3 plain text](https://www.gnu.org/licenses/agpl-3.0.txt)