docs: fix minor typos

Author: chadlwilson

source/partials/release_notes/_release-24-1-0.md.erb

@@ -21,7 +21,7 @@ If you are interested in making this a configurable option to add back the old b
 Java 17 was released in September 2021, and has had complete support within GoCD since version 22.1.0, over 2 years ago.
 Since then it has been packaged with both GoCD container images & installers by default.
 
-This has proven to be be very stable, so to reduce maintenance overhead we are now making Java 17 the minimum supported
+This has proven to be very stable, so to reduce maintenance overhead we are now making Java 17 the minimum supported
 version.
 
 If you are _aiming for minimal agent/server downtime_ in an upgrade to GoCD 24.1.0+, you can do so by following:
@@ -31,9 +31,9 @@ If you are _aiming for minimal agent/server downtime_ in an upgrade to GoCD 24.1
     - If your agents are using GoCD 22.1.0+ from _other install approaches_, they are already Java 17-compatible, _if your server is 21.4.0+_. Ensure they are running with Java 17+.
 1. Ensure your existing server is running with Java 17+.
     - If your server is using GoCD 22.1.0+ from _official GoCD containers or packages_ (RPM, deb)s there is _nothing extra to do_. These already package and run Java 17+.
-    - If your server is using GoCD 21.4.0+ from _other install approaches_, is is already Java 17-compatible, _if your server is 21.4.0+_. Ensure they are running with Java 17+.
+    - If your server is using GoCD 21.4.0+ from _other install approaches_, it is already Java 17-compatible, _if your server is 21.4.0+_. Ensure they are running with Java 17+.
 1. Upgrade your server to GoCD 24.1.0 without worry about Java issues.
-    - Older agents running Java 17+ will re-start automatically against a GoCD 24.1.0 server.
+    - Older agents running Java 17+ will restart automatically against a GoCD 24.1.0 server.
     - You can now validate your installation and agents are working fine.
 1. (Optionally) You can now upgrade your agents to GoCD 24.1.0 whenever you choose.
     - Technically GoCD agent installs are only a "bootstrapper" which downloads the matching agent code from the server for

source/partials/release_notes/_release-25-3-0.md.erb

@@ -7,7 +7,7 @@ need to ensure the certificate your server uses is still trusted by GoCD after t
 earlier versions. This may require importing your certificate authorities into your Java runtime's cacerts store, or
 setting a custom Java trust store <%= link_to 'as discussed here', 'https://github.com/gocd/gocd/discussions/14049#discussioncomment-15233683' %>.
 
-If your server's TLS certifcate is cloud provider managed, or signed by a public Certificate Authority normally
+If your server's TLS certificate is cloud provider managed, or signed by a public Certificate Authority normally
 trusted by operating systems, likely no action is needed.
 
 <h4>Enhancements</h4>

source/partials/release_notes/_release-25-4-0.md.erb

@@ -18,7 +18,7 @@ begin to see warnings after upgrade, you may want to review whether your customi
 <h4>Container image volume tweaks</h4>
 
 For performance reasons, the server and agent container images now declare anonymous volumes for their primary writable directories
-(`/go-working-dir` and `/godata`) on both server and agents. This _should be backward compatiblew_ for the vast
+(`/go-working-dir` and `/godata`) on both server and agents. This _should be backward compatible_ for the vast
 majority of users.
 
 Previously GoCD would use the writeable overlay filesystem to store working data if users did not mount volumes themselves.
@@ -28,7 +28,7 @@ images for most people, especially those running elastic agents; and containers
 
 These volumes will be automatically removed by Kubernetes with either static or elastic agents, and by the <%= link_to 'Docker Elastic Agent plugin', 'https://github.com/gocd-contrib/docker-elastic-agents-plugin' %>.
 However, if you are running the GoCD Server or static agents on Docker (or similar) directly, you may need to <%= link_to 'ensure anonymous volumes are cleaned up', 'https://docs.docker.com/engine/storage/volumes/' %>
-or replace with bind mount volumes to avoid accumlation of volumes over time.
+or replace with bind mount volumes to avoid accumulation of volumes over time.
 
 Note that while not publicly documented, agents previously used `/go` as their working directory, which was changed to
 `/go-working-dir`; consistent with the server. If you were previously intentionally mounting a volume at `/go`, you