fix minor typo (#1498)

Author: alexanderkjall

posts/2025-03-03-Project-Goals-Feb-Update.md

@@ -161,7 +161,7 @@ Next up:
 [RFL.com]: https://rust-for-linux.com/
 [RFL#2]: https://github.com/Rust-for-Linux/linux/issues/2
 
-**What has happened?** We established the precise set of 2025H1 deliverables and we have been tracking them and have begun making progress towards them. Rustdoc has been updated to support extracting doc tests so that the Kernel can execute them in a special environment (this was previously done with a big hack) and RFL is in the process of trying to us that new support. The first PR towards the implementation of [RFC #3716](https://github.com/rust-lang/rfcs/pull/3716) has landed and the ARM team has begun reading early drafts of the design doc for `-Zbuild-core` with the cargo team.
+**What has happened?** We established the precise set of 2025H1 deliverables and we have been tracking them and have begun making progress towards them. Rustdoc has been updated to support extracting doc tests so that the Kernel can execute them in a special environment (this was previously done with a big hack) and RFL is in the process of trying to use that new support. The first PR towards the implementation of [RFC #3716](https://github.com/rust-lang/rfcs/pull/3716) has landed and the ARM team has begun reading early drafts of the design doc for `-Zbuild-core` with the cargo team.
 
 We are also working to finalize the stabilization of the language features that were developed in 2024H2, as two late-breaking complications arose. The first (an interaction between casting of raw pointers and arbitrary self types) is expected to be resolved by limiting the casts of raw pointers, which previously accepted some surprising code. We identified that only a very small set of crates relied on this bug/misfeature; we expect nonetheless to issue a forwards compatibility warning. We are also resolving an issue where `derive(CoercePointee)` was found to reveal the existence of some unstable impls in the stdlib.