From 43ffe87f12b37e5a7f25d8b1724092e177951adb Mon Sep 17 00:00:00 2001
From: "harrisonj2@berea.edu" <jayharrison@Jays-MacBook-Air.local>
Date: Mon, 29 Jun 2026 09:10:36 -0400
Subject: [PATCH] I believe this fixes issue 340 by making the period show in
 the correct place.

---
 source/sec_licensing_existing_communities.ptx | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)

diff --git a/source/sec_licensing_existing_communities.ptx b/source/sec_licensing_existing_communities.ptx
index 66752d7f..1a82ebdc 100644
--- a/source/sec_licensing_existing_communities.ptx
+++ b/source/sec_licensing_existing_communities.ptx
@@ -64,7 +64,7 @@
 		Plausible decided to change licenses from the very permissive <url href="https://mit-license.org/" visual="mit-license.org/">MIT License</url> to the <url href="https://www.fsf.org/bulletin/2021/fall/the-fundamentals-of-the-agplv3" visual="www.fsf.org/bulletin/2021/fall/the-fundamentals-of-the-agplv3">AGPL license</url>, a GNU copyleft license designed to protect rights when the software is being utilized over a network. Simply stated, the AGPLv3 is basically the GPLv3, but with an additional licensing term that requires that users who interact over a network with modified versions of the program can receive the source code for that program.
 	</p>
 	<p>
-		In their blog, Plausible explained that they made the change their license to protect against corporations that took their code and then used it to create and sell proprietary software that directly competed with their project. They had also been approached by some large corporations that wanted Plausible to help them so they could sell a version of Plausible Analytics to their own clients without wanting to contribute anything back to the Plausible project. For more details, see <url href="https://plausible.io/blog/open-source-licenses#risks-associated-with-permissive-open-source-licenses" visual="plausible.io/blog/open-source-licenses#risks-associated-with-permissive-open-source-licenses">Open source licensing and why we're changing Plausible to the AGPL license</url>.
+		In their blog, Plausible explained that they made the change their license to protect against corporations that took their code and then used it to create and sell proprietary software that directly competed with their project. They had also been approached by some large corporations that wanted Plausible to help them so they could sell a version of Plausible Analytics to their own clients without wanting to contribute anything back to the Plausible project. For more details, see <url href="https://plausible.io/blog/open-source-licenses#risks-associated-with-permissive-open-source-licenses" visual="plausible.io/blog/open-source-licenses#risks-associated-with-permissive-open-source-licenses">Open source licensing and why we're changing Plausible to the AGPL license. </url>
 	</p>
 	<p>
 		The kind of situation Plausible found themselves in underscores the importance of licensing, and also the importance of the terms of that license.