Reword for clarity.

Author: LegNeato

content/_index.md

@@ -58,13 +58,11 @@ crates.io ecosystem to GPU programming and provide some sanity.
 
 Additionally, Rust's `no_std` ecosystem offers a wide array of libraries that can be
 used in environments without the standard library. Traditionally this has meant
-embedded devices, but a lot of the same assumptions apply to GPU shaders! As a
+embedded devices, but a lot of the same assumptions apply to GPUs! As a
 consequence, you can reuse [existing `no_std` libraries from
 crates.io](https://crates.io/categories/no-std::no-alloc) in your GPU code _without
 the authors explicitly adding GPU support_. This is uniquely enabled by Rust GPU's
 implementation choices and Rust's
 [registers](https://without.boats/blog/the-registers-of-rust/). Sharing and reusing
 code from the greater Rust ecosystem is a superpower when writing GPU programs that
 will massively compound over time.
-
-

content/blog/2024-08-12-transition-announcement.md

@@ -94,7 +94,7 @@ To put Rust GPU in context, here's an overview of the current landscape:
 
    Additionally, Rust's `no_std` ecosystem offers a wide array of libraries that can be
    used in environments without the standard library. Traditionally this has meant
-   embedded devices, but a lot of the same assumptions apply to GPU shaders! As a
+   embedded devices, but a lot of the same assumptions apply to GPUs! As a
    consequence, you can reuse [existing `no_std` libraries from
    crates.io](https://crates.io/categories/no-std::no-alloc) in your GPU code _without
    the authors explicitly adding GPU support_. This is uniquely enabled by Rust GPU's