From 2b71219a618a8c9ad65cdcf008c2a1c6377eb1cd Mon Sep 17 00:00:00 2001 From: Ryman Date: Mon, 25 Apr 2016 21:01:19 +0100 Subject: [PATCH] libstd: fix typos in thread::LocalKey docs --- src/libstd/thread/local.rs | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) diff --git a/src/libstd/thread/local.rs b/src/libstd/thread/local.rs index 69395001bbfd..6b54ec8afca9 100644 --- a/src/libstd/thread/local.rs +++ b/src/libstd/thread/local.rs @@ -60,7 +60,7 @@ use mem; /// # Platform-specific behavior /// /// Note that a "best effort" is made to ensure that destructors for types -/// stored in thread local storage are run, but not all platforms can gurantee +/// stored in thread local storage are run, but not all platforms can guarantee /// that destructors will be run for all types in thread local storage. For /// example, there are a number of known caveats where destructors are not run: /// @@ -254,7 +254,7 @@ impl LocalKey { /// destruction has completed. Keys without destructors (e.g. with types /// that are `Copy`), may never enter the `Destroyed` state. /// - /// Keys in the `Uninitialized` can be accessed so long as the + /// Keys in the `Uninitialized` state can be accessed so long as the /// initialization does not panic. Keys in the `Valid` state are guaranteed /// to be able to be accessed. Keys in the `Destroyed` state will panic on /// any call to `with`.