Fix some small mistakes in the documentation

houseabsolute · Jan 4, 2025 · be68b5b · be68b5b
1 parent 7e5aced
commit be68b5b
Show file tree

Hide file tree

Showing 2 changed files with 5 additions and 5 deletions.
diff --git a/README.md b/README.md
@@ -151,9 +151,9 @@ executable will use the name of the project instead.
 
 This is a bit inconsistent, but it's how `ubi` has behaved since it was created, and I find this to
 be the sanest behavior. Some projects, for example `rust-analyzer`, provide releases as compressed
-executables with names like `rust-analyzer-x86_64-apple-darwin.gz` and
-`rust-analyzer-x86_64-unknown-linux-musl.gz`, so installing these as `rust-analyzer` seems like
-better behavior.
+executables with names like `rust-analyzer-x86_64-apple-darwin` and
+`rust-analyzer-x86_64-unknown-linux-musl`, so installing these as `rust-analyzer` seems like better
+behavior.
 
 ## How `ubi` Finds the Right Release Artifact
 

diff --git a/ubi/src/lib.rs b/ubi/src/lib.rs
@@ -37,8 +37,8 @@
 //!
 //! This is a bit inconsistent, but it's how `ubi` has behaved since it was created, and I find this
 //! to be the sanest behavior. Some projects, for example `rust-analyzer`, provide releases as
-//! compressed executables with names like `rust-analyzer-x86_64-apple-darwin.gz` and
-//! `rust-analyzer-x86_64-unknown-linux-musl.gz`, so installing these as `rust-analyzer` seems like
+//! executables with names like `rust-analyzer-x86_64-apple-darwin` and
+//! `rust-analyzer-x86_64-unknown-linux-musl`, so installing these as `rust-analyzer` seems like
 //! better behavior.
 //!
 //!