style: Fix typos

Author: epage

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-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`