From 4f30a65b9c03eb09607eb91a929a6396637dc105 Mon Sep 17 00:00:00 2001 From: Brian Bowman Date: Sat, 7 Jan 2017 20:18:59 -0600 Subject: [PATCH] docs: fix spelling of "guaranteed" --- README.md | 4 ++-- src/lib.rs | 4 ++-- 2 files changed, 4 insertions(+), 4 deletions(-) diff --git a/README.md b/README.md index 21567756102..9cd670f1b0f 100644 --- a/README.md +++ b/README.md @@ -674,8 +674,8 @@ This will cause *only* the patch version to be updated upon a `cargo update` cal #### Minimum Version of Rust -`clap` will officially support current stable Rust, minus two releases, but may work with prior releases as well. For example, current stable Rust at the time of this writing is 1.13.0, meaning `clap` is garunteed to compile with 1.11.0 and beyond. -At the 1.14.0 release, `clap` will be garunteed to compile with 1.12.0 and beyond, etc. +`clap` will officially support current stable Rust, minus two releases, but may work with prior releases as well. For example, current stable Rust at the time of this writing is 1.13.0, meaning `clap` is guaranteed to compile with 1.11.0 and beyond. +At the 1.14.0 release, `clap` will be guaranteed to compile with 1.12.0 and beyond, etc. Upon bumping the minimum version of Rust (assuming it's within the stable-2 range), it *must* be clearly annotated in the `CHANGELOG.md` diff --git a/src/lib.rs b/src/lib.rs index d30e2a76a4d..8a1e1ffe1a8 100644 --- a/src/lib.rs +++ b/src/lib.rs @@ -498,8 +498,8 @@ //! //! `clap` will officially support current stable Rust, minus two releases, but may work with prior //! releases as well. For example, current stable Rust at the time of this writing is 1.13.0, -//! meaning `clap` is garunteed to compile with 1.11.0 and beyond. At the 1.14.0 release, `clap` -//! will be garunteed to compile with 2.12.0 and beyond, etc. +//! meaning `clap` is guaranteed to compile with 1.11.0 and beyond. At the 1.14.0 release, `clap` +//! will be guaranteed to compile with 2.12.0 and beyond, etc. //! //! Upon bumping the minimum version of Rust (assuming it's within the stable-2 range), it *must* be //! clearly annotated in the `CHANGELOG.md`