Skip to content

Commit be68b5b

Browse files
committed
Fix some small mistakes in the documentation
1 parent 7e5aced commit be68b5b

File tree

2 files changed

+5
-5
lines changed

2 files changed

+5
-5
lines changed

README.md

Lines changed: 3 additions & 3 deletions
Original file line numberDiff line numberDiff line change
@@ -151,9 +151,9 @@ executable will use the name of the project instead.
151151

152152
This is a bit inconsistent, but it's how `ubi` has behaved since it was created, and I find this to
153153
be the sanest behavior. Some projects, for example `rust-analyzer`, provide releases as compressed
154-
executables with names like `rust-analyzer-x86_64-apple-darwin.gz` and
155-
`rust-analyzer-x86_64-unknown-linux-musl.gz`, so installing these as `rust-analyzer` seems like
156-
better behavior.
154+
executables with names like `rust-analyzer-x86_64-apple-darwin` and
155+
`rust-analyzer-x86_64-unknown-linux-musl`, so installing these as `rust-analyzer` seems like better
156+
behavior.
157157

158158
## How `ubi` Finds the Right Release Artifact
159159

ubi/src/lib.rs

Lines changed: 2 additions & 2 deletions
Original file line numberDiff line numberDiff line change
@@ -37,8 +37,8 @@
3737
//!
3838
//! This is a bit inconsistent, but it's how `ubi` has behaved since it was created, and I find this
3939
//! to be the sanest behavior. Some projects, for example `rust-analyzer`, provide releases as
40-
//! compressed executables with names like `rust-analyzer-x86_64-apple-darwin.gz` and
41-
//! `rust-analyzer-x86_64-unknown-linux-musl.gz`, so installing these as `rust-analyzer` seems like
40+
//! executables with names like `rust-analyzer-x86_64-apple-darwin` and
41+
//! `rust-analyzer-x86_64-unknown-linux-musl`, so installing these as `rust-analyzer` seems like
4242
//! better behavior.
4343
//!
4444
//!

0 commit comments

Comments
 (0)