style: Fix typos

content/GATs-stabilization-push/index.md

@@ -171,7 +171,7 @@ Ok, so now comes the part that nobody likes hearing about: the limitations. Fort
 fn takes_iter(_: &mut dyn for<'a> LendingIterator<Item<'a> = &'a i32>) {}
 ```
 
-The biggest reason for this decision is that there's still a bit of design and implementation work to actually make this usable. And while this is a nice feature, adding this in the future would be a backward-compatible change. We feel that it's better to get *most* of GATs stabilized and then come back and try to tackle this later than to block GATs for even longer. Also, GATs without object safety are still very powerful, so we don't lose much by defering this.
+The biggest reason for this decision is that there's still a bit of design and implementation work to actually make this usable. And while this is a nice feature, adding this in the future would be a backward-compatible change. We feel that it's better to get *most* of GATs stabilized and then come back and try to tackle this later than to block GATs for even longer. Also, GATs without object safety are still very powerful, so we don't lose much by deferring this.
 
 As was mentioned earlier in this post, there are still a couple remaining diagnostics [issues](https://github.com/rust-lang/rust/labels/F-generic_associated_types). If you do find bugs though, please file issues!
 

content/Increasing-Rusts-Reach-2018.md

@@ -22,7 +22,7 @@ three (3) months, from mid-May to mid-August. Each partnership agrees to a commi
 3-5 hours per week collaborating on a Rust project.
 
 By way of thanks for participating in the program, we offer a fully paid conference ticket,
-travel, and accomodations for every participant to a Rust Conference of their choice:
+travel, and accommodations for every participant to a Rust Conference of their choice:
 
 - May 26-27: [RustFest Paris]
 - August 16-17: [RustConf]

content/Project-Goals-2025-July-Update.md

@@ -1644,7 +1644,7 @@ The `stable_mir` crate is now `rustc_public`. We are now finalizing the infrastr
 </div>
 <!-- markdown separator -->
 
-We made further progress on the new benchmarking scheme. The side of the website is nearing MVP status, currently we are switching focus on the side of the collector tha truns the benchmarks.
+We made further progress on the new benchmarking scheme. The side of the website is nearing MVP status, currently we are switching focus on the side of the collector that runs the benchmarks.
 
 Some notable PRs:
 - Benchmark request queue for try builds and release artifacts (<https://github.com/rust-lang/rustc-perf/pull/2166>, <https://github.com/rust-lang/rustc-perf/pull/2192>, <https://github.com/rust-lang/rustc-perf/pull/2197>, <https://github.com/rust-lang/rustc-perf/pull/2201>).
@@ -1669,7 +1669,7 @@ Some notable PRs:
 
 <!-- this comment helps to convince the markdown parser to do the right thing -->
 
-We made further progress on the new benchmarking scheme. The side of the website is nearing MVP status, currently we are switching focus on the side of the collector tha truns the benchmarks.
+We made further progress on the new benchmarking scheme. The side of the website is nearing MVP status, currently we are switching focus on the side of the collector that runs the benchmarks.
 
 Some notable PRs:
 - Benchmark request queue for try builds and release artifacts (https://github.com/rust-lang/rustc-perf/pull/2166, https://github.com/rust-lang/rustc-perf/pull/2192, https://github.com/rust-lang/rustc-perf/pull/2197, https://github.com/rust-lang/rustc-perf/pull/2201).

content/Project-Goals-Dec-Update.md

@@ -47,7 +47,7 @@ For our other goals, we made progress, but there remains work to be done:
 We largely completed our goal to stabilize the language features used by the Rust for Linux project. In some cases a small amount of work remains. Over the last six months, we...
 
 * stabilized the `offset_of!` macro to get the offset of fields;
-* *almost* stabilized the `CoercePointee` trait -- but [discovered that the current implementaton was revealing unstable details](https://github.com/rust-lang/rust/pull/133820#issuecomment-2559379796), which is currently being resolved;
+* *almost* stabilized the `CoercePointee` trait -- but [discovered that the current implementation was revealing unstable details](https://github.com/rust-lang/rust/pull/133820#issuecomment-2559379796), which is currently being resolved;
 * `asm_goto` stabilization PR and reference updates are up, excluding the "output" feature.
 * completed the majority of the work for arbitrary self types, which is being used by RfL and just needs documentation before stabilisation
 

content/Project-Goals-Feb-Update/index.md

@@ -173,7 +173,7 @@ We are also working to finalize the stabilization of the language features that
 
 
 <details>
-<summary>3 detailed updates availabled.</summary>
+<summary>3 detailed updates available.</summary>
 
 <!-- this comment helps to convince the markdown parser to do the right thing -->
 
@@ -284,7 +284,7 @@ Updates from our [2025-02-12 meeting](https://hackmd.io/AkNBW942SoacLayPXHthCg):
 
 Given the recent controversy about Rust usage in the Kernel, the RFL group wrote up a [policy document explainer](https://rust-for-linux.com/rust-kernel-policy) to explain the policy, and there was a [write-up on LWN](https://lwn.net/SubscriberLink/1007921/9020dbb12585d48f/).
 
-Regarding arbitary self types and coerce pointee, we are waiting on rust-lang/rust#136764 and rust-lang/rust#136776. The former is on lang team FCP. The latter has received approval from lang team and is awaiting further impl work by @BoxyUwU.
+Regarding arbitrary self types and coerce pointee, we are waiting on rust-lang/rust#136764 and rust-lang/rust#136776. The former is on lang team FCP. The latter has received approval from lang team and is awaiting further impl work by @BoxyUwU.
 
 @ojeda is looking into how to manage dependency information and configure no-std externally.
 
@@ -349,7 +349,7 @@ Help wanted: this project goal needs a compiler developer to move forward.
 *Help wanted:* this project goal needs someone to work on the implementation. If you'd like to help, please post in [this goal's dedicated zulip topic](https://rust-lang.zulipchat.com/#narrow/channel/435869-project-goals/topic/Prototype.20a.20new.20set.20of.20Cargo.20.22plumbing.22.20.28goals.23264.29).
 
 <details>
-<summary>2 detailed updates availabled.</summary>
+<summary>2 detailed updates available.</summary>
 
 <!-- this comment helps to convince the markdown parser to do the right thing -->
 
@@ -947,7 +947,7 @@ This is, I believe, mostly waiting on us on the lang team to have a look, probab
 
 
 <details>
-<summary>2 detailed updates availabled.</summary>
+<summary>2 detailed updates available.</summary>
 
 <!-- this comment helps to convince the markdown parser to do the right thing -->
 
@@ -1004,7 +1004,7 @@ Update (2025-02-27):
 
 
 <details>
-<summary>2 detailed updates availabled.</summary>
+<summary>2 detailed updates available.</summary>
 
 <!-- this comment helps to convince the markdown parser to do the right thing -->
 
@@ -1393,7 +1393,7 @@ Last week at the Safety Critical Rust Consortium meeting in London, Ferrous syst
 
 
 <details>
-<summary>2 detailed updates availabled.</summary>
+<summary>2 detailed updates available.</summary>
 
 <!-- this comment helps to convince the markdown parser to do the right thing -->
 

content/Rust-1.13/index.md

@@ -177,7 +177,7 @@ part of our toolbox!
 
 We can use this tool to look at a [graph] of performance over the 1.13
 development cycle, shown below. This cycle covered the dates from August 16
-through September 29 (the graph begins from Augest 25th though and is filtered
+through September 29 (the graph begins from August 25th though and is filtered
 in a few ways to eliminate bogus, incomplete, or confusing results). There
 appear to be some big reductions, which are quantified on the corresponding
 [statistics] page.

content/Rust-1.16.md

@@ -52,7 +52,7 @@ There's a lot of them. However, you can think of this process in two big steps:
 all of its safety checks, makes sure your syntax is correct, all that stuff. Second, once it's satisfied
 that everything is in order, it produces the actual binary code that you end up executing.
 
-It turns out that that second step takes a lot of time. And most of the time, it's not neccesary. That is,
+It turns out that that second step takes a lot of time. And most of the time, it's not necessary. That is,
 when you're working on some Rust code, many developers will get into a workflow like this:
 
  1. Write some code.

content/Rust-1.17.md

@@ -166,7 +166,7 @@ step back we want to regretfully inform you about. On Windows, Visual
 Studio 2017 has been released, and Microsoft has changed the structure
 of how the software is installed. [Rust cannot automatically detect this
 location](https://github.com/rust-lang/rust/issues/38584), and while we
-were working on the neccesary changes, they did not make it in time for
+were working on the necessary changes, they did not make it in time for
 this release. Until then, Visual Studio 2015 still works fine, or you
 can run `vcvars.bat` on the command line. We hope to make this work
 in a seamless fashion soon.
@@ -319,7 +319,7 @@ tools = []
 ```
 
 The `tools` feature allows us to include extra tooling, and the `postgres` and `sqlite`
-features control which databses we want to support.
+features control which databases we want to support.
 
 Previously, `cargo build` would attempt to build all targets, which is normally what
 you want. But what if we had a `src/bin/postgres-tool.rs`, that would only really

content/Rust-1.24.1.md

@@ -54,7 +54,7 @@ in 1.24.0, you'll need to revert it for now.  While we still plan to introduce
 this behavior eventually, we will be rolling it out more slowly and with a new
 implementation strategy.
 
-Quoting [the 1.24 annoucement](https://blog.rust-lang.org/2018/02/15/Rust-1.24.html):
+Quoting [the 1.24 announcement](https://blog.rust-lang.org/2018/02/15/Rust-1.24.html):
 
 > There’s one other change we’d like to talk about here: undefined behavior.
 > Rust generally strives to minimize undefined behavior, having none of it in
@@ -120,7 +120,7 @@ into Lua is [wrapped with `lua_pcall`](https://www.lua.org/pil/24.3.2.html):
 So, the question becomes: Why does this break? And why does it break on
 Windows?
 
-When we talked about `setjmp`/`longjmp` inititally, a key phrase here wasn't
+When we talked about `setjmp`/`longjmp` initially, a key phrase here wasn't
 highlighted. Here it is:
 
 > After digging in, the culpurit was found: `setjmp`/`longjmp`. These functions
@@ -192,7 +192,7 @@ we may backport, otherwise, this functionality will be back in 1.26.
 TL;DR: `rustc` stopped working for some Windows users in edge-case situations.
 If it's been working for you, you were not affected by this bug.
 
-In constrast with the previous bug, which is very complex and tough to understand,
+In contrast with the previous bug, which is very complex and tough to understand,
 this bug's impact is simple: if you have non-ASCII paths in the directory where
 you invoke `rustc`, in 1.24, it would incorrectly error with a message like
 

content/Rust-1.32.0.md

@@ -125,7 +125,7 @@ n: 6
 n: 24
 ```
 
-This is servicable, but not particularly great. Maybe we could work on how we
+This is serviceable, but not particularly great. Maybe we could work on how we
 print out the context to make it more clear, but now we're not debugging our code,
 we're figuring out how to make our debugging code better.
 
@@ -161,7 +161,7 @@ Because the `dbg!` macro returns the value of what it's debugging, instead of
 of our code. Additionally, we have *vastly* more useful output.
 
 That's a lot to say about a little macro, but we hope it improves your
-debugging experience! We are contining to work on support for `gdb` and
+debugging experience! We are continuing to work on support for `gdb` and
 friends as well, of course.
 
 #### `jemalloc` is removed by default

content/Rust-1.34.1.md

@@ -45,7 +45,7 @@ In the following snippet, the method `required` expects `dep: &D` but the actual
 dependencies.iter().filter(|dep| dep.required());
 ```
 
-Clippy erronously suggested `.filter(Dependency::required)`,
+Clippy erroneously suggested `.filter(Dependency::required)`,
 which is rejected by the compiler due to the difference in borrows.
 
 ### False positive in `clippy::missing_const_for_fn`

content/Rust-1.60.0/index.md

@@ -41,7 +41,7 @@ RUSTFLAGS="-C instrument-coverage" cargo build
 
 After that, you can run the resulting binary, which will produce a
 `default.profraw` file in the current directory. (The path and filename can be
-overriden by an environment variable; see
+overridden by an environment variable; see
 [documentation](https://doc.rust-lang.org/stable/rustc/instrument-coverage.html#running-the-instrumented-binary-to-generate-raw-coverage-profiling-data)
 for details).
 

content/Rustup-1.20.0.md

@@ -46,7 +46,7 @@ To change the rustup profile you can use the `rustup set profile` command. For e
 rustup set profile minimal
 ```
 
-It's also possible to choose the profile when installing rustup for the first time, either interactively by choosing the "Customize installation" option or programmaticaly by passing the `--profile=<name>` flag. Profiles will only affect newly installed toolchains: as usual it will be possible to install individual components later with: `rustup component add`.
+It's also possible to choose the profile when installing rustup for the first time, either interactively by choosing the "Customize installation" option or programmatically by passing the `--profile=<name>` flag. Profiles will only affect newly installed toolchains: as usual it will be possible to install individual components later with: `rustup component add`.
 
 ### Installing the latest compatible nightly
 

content/Rustup-1.24.3.md

@@ -26,7 +26,7 @@ If you don't have it already, you can [get rustup][install] from the appropriate
 
 ## What's new in rustup 1.24.3
 
-This patch release focusses around resolving some regressions in behaviour in
+This patch release focuses around resolving some regressions in behaviour in
 the 1.24.x series, in either low tier platforms, or unusual situations around
 very old toolchains.
 

content/Security-advisory.md

@@ -82,7 +82,7 @@ resolve this in the standard library soon.
 ## Timeline of events
 
 * Thu, May  9, 2019 at 14:07 PM - Bug reported to security@rust-lang.org
-* Thu, May  9, 2019 at 15:10 PM - Alex reponds, confirming the bug
+* Thu, May  9, 2019 at 15:10 PM - Alex responds, confirming the bug
 * Fri, May 10, 2019 - Plan for mitigation developed and implemented
 * Mon, May 13, 2019 - PRs posted to GitHub for [stable][3]/[beta][4]/[master][5] branches
 * Mon, May 13, 2019 - Security list informed of this issue

content/all-hands.md

@@ -121,7 +121,7 @@ process].
 ### WG: network services
 
 - [WG overview slides](https://gist.github.com/withoutboats/6d4c4639b286d3da19d89d8af82d82d7).
-- **Launching the WG**: determined goals for the WG, including async/await, documentaiton, mid-level HTTP libraries, and the [Tower](https://github.com/tower-rs/tower) ecosystem.
+- **Launching the WG**: determined goals for the WG, including async/await, documentation, mid-level HTTP libraries, and the [Tower](https://github.com/tower-rs/tower) ecosystem.
   Kickoff announcement coming soon!
 - **Async/await**: finalized design and stabilization approach for RFCs (blog post and links to RFCs [here](https://boats.gitlab.io/blog/post/2018-04-06-async-await-final/)).
 

content/cargo-cves.md

@@ -13,7 +13,7 @@ aliases = ["2022/09/14/cargo-cves.html"]
 The Rust Security Response WG was notified that Cargo did not prevent
 extracting some malformed packages downloaded from alternate registries. An
 attacker able to upload packages to an alternate registry could fill the
-filesystem or corrupt arbitary files when Cargo downloaded the package.
+filesystem or corrupt arbitrary files when Cargo downloaded the package.
 
 These issues have been assigned CVE-2022-36113 and CVE-2022-36114. The severity
 of these vulnerabilities is "low" for users of alternate registries. Users
@@ -30,7 +30,7 @@ macros.
 
 After a package is downloaded, Cargo extracts its source code in the `~/.cargo`
 folder on disk, making it available to the Rust projects it builds. To record
-when an extraction is successfull, Cargo writes "ok" to the `.cargo-ok` file at
+when an extraction is successful, Cargo writes "ok" to the `.cargo-ok` file at
 the root of the extracted source code once it extracted all the files.
 
 It was discovered that Cargo allowed packages to contain a `.cargo-ok`
@@ -60,7 +60,7 @@ their own toolchains.
 
 ## Mitigations
 
-We recommend users of alternate registries to excercise care in which package
+We recommend users of alternate registries to exercise care in which package
 they download, by only including trusted dependencies in their projects. Please
 note that even with these vulnerabilities fixed, by design Cargo allows
 arbitrary code execution at build time thanks to build scripts and procedural
@@ -69,7 +69,7 @@ vulnerabilities.
 
 crates.io implemented server-side checks to reject these kinds of packages
 years ago, and there are no packages on crates.io exploiting these
-vulnerabilities. crates.io users still need to excercise care in choosing their
+vulnerabilities. crates.io users still need to exercise care in choosing their
 dependencies though, as the same concerns about build scripts and procedural
 macros apply here.
 

content/conf-lineup@1.md

@@ -21,15 +21,15 @@ The second day is the main event, with [talks][rc-talks] at every
 level of expertise, covering basic and advanced techniques, experience
 reports, guidance on teaching, and interesting libraries.
 
-[Tickets are still on sale!][rc-ticks] We offer a [scholarship][rc-schol] for those
+[Tickets are still on sale!][rc-ticks] We offer a [scholarship][rc-scholar] for those
 who would otherwise find it difficult to attend. Join us in lovely Portland and
 hear about the latest developments in the Rust world!
 
 Follow us on Twitter [@rustconf](https://twitter.com/rustconf).
 
  [rc-talks]: http://rustconf.com/program.html
  [rc-ticks]: http://rustconf.com/register.html
- [rc-schol]: https://tilde.wufoo.com/forms/rustconf-scholarships/
+ [rc-scholar]: https://tilde.wufoo.com/forms/rustconf-scholarships/
 
 ### April 29-30th & Sept 30-01: Rust Fest
 

content/const-eval-safety-rule-revision.md

@@ -121,7 +121,7 @@ The details of the CTFE engine's value representation do not matter too much for
 discussion here. We merely note that earlier versions of the compiler silently
 accepted expressions that *seemed to* transmute memory addresses into integers,
 copied them around, and then transmuted them back into addresses; but that was
-not what was acutally happening under the hood. Instead, what was happening was
+not what was actually happening under the hood. Instead, what was happening was
 that the values were passed around blindly (after all, the whole point of
 transmute is that it does no transformation on its input value, so it is a no-op
 in terms of its operational semantics).
@@ -274,7 +274,7 @@ We have [performed][crater results] a [crater run] for the 1.64-beta and that di
 instances of this particular problem.
 If you can test compiling your crate atop the 1.64-beta before the stable
 release goes out on September 22nd, all the better! One easy way to try the beta
-is to use [rustup's override shortand][rustup] for it:
+is to use [rustup's override shorthand][rustup] for it:
 
 ```sh
 $ rustup update beta

content/crates.io-malicious-crates-fasterlog-and-asyncprintln.md

@@ -18,7 +18,7 @@ These crates were:
 - `faster_log` - Published on May 25th, 2025, downloaded 7181 times
 - `async_println` - Published on May 25th, 2025, downloaded 1243 times
 
-The malicious code was executed at runtime, when running or testing a project depending on them. Notably, they did not execute any malicious code at build time. Except for their malicious payload, these crates copied the source code, features, and documentation of legitimate crates, using a similiar name to them (a case of typosquatting[^typosquatting]).
+The malicious code was executed at runtime, when running or testing a project depending on them. Notably, they did not execute any malicious code at build time. Except for their malicious payload, these crates copied the source code, features, and documentation of legitimate crates, using a similar name to them (a case of typosquatting[^typosquatting]).
 
 ## Actions taken