From df9b23c96a38149f3ae6c8580463345d4a146758 Mon Sep 17 00:00:00 2001 From: Felix Rabe Date: Fri, 27 Jul 2018 20:59:53 +0200 Subject: [PATCH] Typo: retreiv... -> retriev... (#614) --- src/lib.rs | 8 ++++---- src/platform/windows/events_loop.rs | 2 +- 2 files changed, 5 insertions(+), 5 deletions(-) diff --git a/src/lib.rs b/src/lib.rs index 1051b959..a8b0abb0 100644 --- a/src/lib.rs +++ b/src/lib.rs @@ -25,11 +25,11 @@ //! Once a window has been created, it will *generate events*. For example whenever the user moves //! the window, resizes the window, moves the mouse, etc. an event is generated. //! -//! The events generated by a window can be retreived from the `EventsLoop` the window was created +//! The events generated by a window can be retrieved from the `EventsLoop` the window was created //! with. //! //! There are two ways to do so. The first is to call `events_loop.poll_events(...)`, which will -//! retreive all the events pending on the windows and immediately return after no new event is +//! retrieve all the events pending on the windows and immediately return after no new event is //! available. You usually want to use this method in application that render continuously on the //! screen, such as video games. //! @@ -80,7 +80,7 @@ //! # Drawing on the window //! //! Winit doesn't provide any function that allows drawing on a window. However it allows you to -//! retreive the raw handle of the window (see the `os` module for that), which in turn allows you +//! retrieve the raw handle of the window (see the `os` module for that), which in turn allows you //! to create an OpenGL/Vulkan/DirectX/Metal/etc. context that will draw on the window. //! @@ -166,7 +166,7 @@ pub struct WindowId(platform::WindowId); #[derive(Debug, Copy, Clone, PartialEq, Eq, PartialOrd, Ord, Hash)] pub struct DeviceId(platform::DeviceId); -/// Provides a way to retreive events from the system and from the windows that were registered to +/// Provides a way to retrieve events from the system and from the windows that were registered to /// the events loop. /// /// An `EventsLoop` can be seen more or less as a "context". Calling `EventsLoop::new()` diff --git a/src/platform/windows/events_loop.rs b/src/platform/windows/events_loop.rs index ca90c4db..ca9a8f05 100644 --- a/src/platform/windows/events_loop.rs +++ b/src/platform/windows/events_loop.rs @@ -357,7 +357,7 @@ lazy_static! { } }; // Message sent when we want to execute a closure in the thread. - // WPARAM contains a Box> that must be retreived with `Box::from_raw`, + // WPARAM contains a Box> that must be retrieved with `Box::from_raw`, // and LPARAM is unused. static ref EXEC_MSG_ID: u32 = { unsafe {