From b064be1d3372e3c5ee91fc6ee4fb1ee091c662b5 Mon Sep 17 00:00:00 2001 From: Jost Alemann Date: Mon, 14 Jul 2025 00:36:45 +0200 Subject: [PATCH] fix: typos --- content/en-US/download/community-mirrors.smd | 4 ++-- content/en-US/learn/build-system.smd | 2 +- content/en-US/news/fosdem-2021.smd | 2 +- 3 files changed, 4 insertions(+), 4 deletions(-) diff --git a/content/en-US/download/community-mirrors.smd b/content/en-US/download/community-mirrors.smd index 46d2ad7c0..d196a5a0a 100644 --- a/content/en-US/download/community-mirrors.smd +++ b/content/en-US/download/community-mirrors.smd @@ -76,9 +76,9 @@ Written more precisely, here is the key information and recommend workflow for d * Source tarballs, bootstrap tarballs, and binary tarballs are available from all listed mirrors, as well as minisign signatures for all such files. * Binary tarballs for recent Zig versions are of the form `zig-x86_64-linux-0.14.1.tar.xz`. * If a mirror responds with a HTTP status code other than 200 OK: - * `503 Unavilable` may indicate scheduled downtime. + * `503 Unavailable` may indicate scheduled downtime. * `429 Too Many Requests` may indicate intentional rate-limiting. - * `404 Not Found` is a permitted response when requesting Zig releses 0.5.0 or earlier, or Zig development builds earlier than the current latest release. + * `404 Not Found` is a permitted response when requesting Zig releases 0.5.0 or earlier, or Zig development builds earlier than the current latest release. * Otherwise, feel free to [open an issue](https://github.com/ziglang/www.ziglang.org/issues/new) to inform us of the problem. * The Zig Software Foundation can never guarantee the security of any mirror, so every time a tarball is downloaded, it is **essential** to also download the minisign signature (suffix the filename with ".minisig") and verify it against the ZSF's public key (which you should copy from the ziglang.org/download page). **Never skip this step.** * If a mirror responds with `200 OK` but signature validation fails on the returned tarball, feel free to [open an diff --git a/content/en-US/learn/build-system.smd b/content/en-US/learn/build-system.smd index 39a46acb8..0b35b559f 100644 --- a/content/en-US/learn/build-system.smd +++ b/content/en-US/learn/build-system.smd @@ -16,7 +16,7 @@ layer of abstraction to manage the complexity of building from source. For example, perhaps one of these situations applies: -- The command line becomes too long and unwieldly, and you want some place to +- The command line becomes too long and unwieldy, and you want some place to write it down. - You want to build many things, or the build process contains many steps. - You want to take advantage of concurrency and caching to reduce build time. diff --git a/content/en-US/news/fosdem-2021.smd b/content/en-US/news/fosdem-2021.smd index 765460f8e..76569f73d 100644 --- a/content/en-US/news/fosdem-2021.smd +++ b/content/en-US/news/fosdem-2021.smd @@ -27,7 +27,7 @@ We're interested in all kinds of talks about Zig, of course! If you want to make All submissions must be made through [FOSDEM's pentabarf website](https://penta.fosdem.org/). Make sure to select the "Zig Programming Language Devroom" when submitting. -**You must also make sure to be able to fullfill all requirements to be able to present, as listed in the next section.** [Here you can sign up](https://penta.fosdem.org/user/new_account). +**You must also make sure to be able to fulfill all requirements to be able to present, as listed in the next section.** [Here you can sign up](https://penta.fosdem.org/user/new_account). ### Prerequisites & Talk details