diff --git a/src/dpi.rs b/src/dpi.rs index bf234007b9..3c3829359f 100644 --- a/src/dpi.rs +++ b/src/dpi.rs @@ -77,7 +77,7 @@ //! currently uses a three-pronged approach: //! + Use the value in the `WINIT_X11_SCALE_FACTOR` environment variable, if present. //! + If not present, use the value set in `Xft.dpi` in Xresources. -//! + Otherwise, calcuate the scale factor based on the millimeter monitor dimensions provided by XRandR. +//! + Otherwise, calculate the scale factor based on the millimeter monitor dimensions provided by XRandR. //! //! If `WINIT_X11_SCALE_FACTOR` is set to `randr`, it'll ignore the `Xft.dpi` field and use the //! XRandR scaling method. Generally speaking, you should try to configure the standard system diff --git a/src/event_loop.rs b/src/event_loop.rs index 890e4e560e..dc95934f5a 100644 --- a/src/event_loop.rs +++ b/src/event_loop.rs @@ -383,7 +383,7 @@ impl fmt::Display for EventLoopClosed { impl error::Error for EventLoopClosed {} -/// Fiter controlling the propagation of device events. +/// Filter controlling the propagation of device events. #[derive(Copy, Clone, PartialEq, Eq, PartialOrd, Ord, Hash, Debug)] pub enum DeviceEventFilter { /// Always filter out device events. diff --git a/src/platform_impl/android/mod.rs b/src/platform_impl/android/mod.rs index 31972b81c3..405130fcd9 100644 --- a/src/platform_impl/android/mod.rs +++ b/src/platform_impl/android/mod.rs @@ -881,7 +881,7 @@ impl MonitorHandle { } pub fn refresh_rate_millihertz(&self) -> Option { - // FIXME no way to get real refrsh rate for now. + // FIXME no way to get real refresh rate for now. None } diff --git a/src/platform_impl/linux/wayland/event_loop/mod.rs b/src/platform_impl/linux/wayland/event_loop/mod.rs index 491883ab58..8fe13bdee0 100644 --- a/src/platform_impl/linux/wayland/event_loop/mod.rs +++ b/src/platform_impl/linux/wayland/event_loop/mod.rs @@ -64,7 +64,7 @@ pub struct EventLoopWindowTarget { /// Theme manager to manage cursors. /// - /// It's being shared amoung all windows to avoid loading + /// It's being shared between all windows to avoid loading /// multiple similar themes. pub theme_manager: ThemeManager, diff --git a/src/platform_impl/linux/wayland/window/mod.rs b/src/platform_impl/linux/wayland/window/mod.rs index 18bbee541b..c061352872 100644 --- a/src/platform_impl/linux/wayland/window/mod.rs +++ b/src/platform_impl/linux/wayland/window/mod.rs @@ -90,7 +90,7 @@ impl Window { .create_surface_with_scale_callback(move |scale, surface, mut dispatch_data| { let winit_state = dispatch_data.get::().unwrap(); - // Get the window that receiced the event. + // Get the window that received the event. let window_id = super::make_wid(&surface); let mut window_update = winit_state.window_updates.get_mut(&window_id).unwrap(); diff --git a/src/platform_impl/linux/x11/ime/input_method.rs b/src/platform_impl/linux/x11/ime/input_method.rs index 5a1695cb0e..a747f972a9 100644 --- a/src/platform_impl/linux/x11/ime/input_method.rs +++ b/src/platform_impl/linux/x11/ime/input_method.rs @@ -180,10 +180,10 @@ impl PotentialInputMethod { } // By logging this struct, you get a sequential listing of every locale modifier tried, where it -// came from, and if it succceeded. +// came from, and if it succeeded. #[derive(Debug, Clone)] pub struct PotentialInputMethods { - // On correctly configured systems, the XMODIFIERS environemnt variable tells us everything we + // On correctly configured systems, the XMODIFIERS environment variable tells us everything we // need to know. xmodifiers: Option, // We have some standard options at our disposal that should ostensibly always work. For users @@ -213,7 +213,7 @@ impl PotentialInputMethods { // that case, we get `None` and end up skipping ahead to the next method. xmodifiers, fallbacks: [ - // This is a standard input method that supports compose equences, which should + // This is a standard input method that supports compose sequences, which should // always be available. `@im=none` appears to mean the same thing. PotentialInputMethod::from_str("@im=local"), // This explicitly specifies to use the implementation-dependent default, though diff --git a/src/platform_impl/linux/x11/mod.rs b/src/platform_impl/linux/x11/mod.rs index 6ee2fb827d..ff6f012338 100644 --- a/src/platform_impl/linux/x11/mod.rs +++ b/src/platform_impl/linux/x11/mod.rs @@ -457,7 +457,7 @@ impl EventLoop { // must do this because during the execution of the iteration we sometimes wake // the mio waker, and if the waker is already awaken before we call poll(), // then poll doesn't block, but it returns immediately. This caused the event - // loop to run continously even if the control_flow was `Wait` + // loop to run continuously even if the control_flow was `Wait` continue; } } diff --git a/src/platform_impl/linux/x11/util/window_property.rs b/src/platform_impl/linux/x11/util/window_property.rs index 8bf718ea8e..e93d5bb072 100644 --- a/src/platform_impl/linux/x11/util/window_property.rs +++ b/src/platform_impl/linux/x11/util/window_property.rs @@ -58,7 +58,7 @@ impl XConnection { property, // This offset is in terms of 32-bit chunks. offset, - // This is the quanity of 32-bit chunks to receive at once. + // This is the quantity of 32-bit chunks to receive at once. PROPERTY_BUFFER_SIZE, ffi::False, property_type, diff --git a/src/platform_impl/web/event_loop/runner.rs b/src/platform_impl/web/event_loop/runner.rs index 840ba558e6..fd9a2e850e 100644 --- a/src/platform_impl/web/event_loop/runner.rs +++ b/src/platform_impl/web/event_loop/runner.rs @@ -65,7 +65,7 @@ impl Runner { } } - /// Returns the cooresponding `StartCause` for the current `state`, or `None` + /// Returns the corresponding `StartCause` for the current `state`, or `None` /// when in `Exit` state. fn maybe_start_cause(&self) -> Option { Some(match self.state { diff --git a/src/window.rs b/src/window.rs index 50bc252618..a3598ff54c 100644 --- a/src/window.rs +++ b/src/window.rs @@ -625,7 +625,7 @@ impl Window { self.window.set_visible(visible) } - /// Gets the window's current vibility state. + /// Gets the window's current visibility state. /// /// `None` means it couldn't be determined, so it is not recommended to use this to drive your rendering backend. ///