From 476de329b383f8154fdc372b63edc4c74a20f1d3 Mon Sep 17 00:00:00 2001 From: Mikayla Date: Sat, 20 Jan 2024 20:19:01 -0800 Subject: [PATCH] Fix issues in element comment --- crates/gpui/src/element.rs | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) diff --git a/crates/gpui/src/element.rs b/crates/gpui/src/element.rs index 379376f201b7d1f1824fefe58322eaac01941b62..0c98820d306c7433ab7d3170a95c923806977461 100644 --- a/crates/gpui/src/element.rs +++ b/crates/gpui/src/element.rs @@ -29,9 +29,9 @@ //! With great power, comes great responsibility. //! //! However, most of the time, you won't need to implement your own elements. GPUI provides a number of -//! elements that should cover most common use cases out of the box and it's recommended that you use those. +//! elements that should cover most common use cases out of the box and it's recommended that you use those //! to construct `components`, using the `RenderOnce` trait and the `#[derive(IntoElement)]` macro. Only implement -//! components when you need to take manual control of the layout and painting process, such as when using +//! elements when you need to take manual control of the layout and painting process, such as when using //! your own custom layout algorithm or rendering a code editor. use crate::{