From addf8ca942a85e6a061e8315afbe90c95ae4b3e4 Mon Sep 17 00:00:00 2001
From: Michael Angerman <1809991+stormasm@users.noreply.github.com>
Date: Wed, 20 Sep 2023 20:34:25 -0700
Subject: [PATCH] update the doc in toolchain.toml describing the update plan
 (#10453)

The *toolchain.toml* doc incorrectly stated how many releases behind
stable we will be...

It said we would be 1 release behind when actually we want to be 2
releases behind stable.
---
 rust-toolchain.toml | 4 ++--
 1 file changed, 2 insertions(+), 2 deletions(-)

diff --git a/rust-toolchain.toml b/rust-toolchain.toml
index 8bd7affd32..45d35de0ac 100644
--- a/rust-toolchain.toml
+++ b/rust-toolchain.toml
@@ -9,8 +9,8 @@
 # The default profile includes rustc, rust-std, cargo, rust-docs, rustfmt and clippy.
 # https://rust-lang.github.io/rustup/concepts/profiles.html
 profile = "default"
-# The current plan is to be 1 release behind the latest stable release. So, if the
-# latest stable release is 1.62.0, the channel should be 1.61.0. We want to do this
+# The current plan is to be 2 releases behind the latest stable release. So, if the
+# latest stable release is 1.72.0, the channel should be 1.70.0. We want to do this
 # so that we give repo maintainers and package managers a chance to update to a more
 # recent version of rust. However, if there is a "cool new feature" that we want to
 # use in nushell, we may opt to use the bleeding edge stable version of rust.