Status/2026Q1: spell

website/content/en/status/report-2026-01-2026-03/bugmeister.adoc

@@ -15,7 +15,7 @@ We welcomed a new member of the Triage Team, Simon Wollwage, who has been loving
 Many reports have been closed or had their underlying issues fixed from his efforts, and we thank him.
 
 We finished updating documentation to request that proposed changes are sent as git format patches.
-This will save time, increase secuirty, and properly convey author metadata.
+This will save time, increase security, and properly convey author metadata.
 If we missed a spot, please let us know.
 
 See also: link:https://wiki.freebsd.org/Bugzilla/SearchQueries[]

website/content/en/status/report-2026-01-2026-03/buildpacks.adoc

@@ -19,7 +19,7 @@ Since the last report in 2025Q1, the project has transitioned from experimental
 
 The next steps focus on lowering the barrier to entry for developers and improving the automation of the FreeBSD build path:
 
-* Seek a FreeBSD ports commiter to review and land the link:https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=292952[new port sysutils/pack] into the ports tree.
+* Seek a FreeBSD ports committer to review and land the link:https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=292952[new port sysutils/pack] into the ports tree.
 * Address a link:https://github.com/buildpacks/pack/issues/2546[known issue] in `pack builder create` where the tool incorrectly attempts to use non-FreeBSD URLs for certain binary downloads.
 * Investigate creating link:https://paketo.io[Paketo-style buildpacks] specifically for FreeBSD.
   This would provide 'zero-config' builds for popular languages (e.g., Go) that produce FreeBSD-native binaries within containers.