From 291f35308513969f552864813005fe21893a09f2 Mon Sep 17 00:00:00 2001 From: Patrick Dubroy Date: Wed, 24 Jan 2024 19:21:08 +0100 Subject: [PATCH] Fix `registers` link in README.md (#5389) It looked to me that `registers` was intended to be a link here...if I'm wrong, feel free to ignore :-) Release Notes: - N/A --- crates/gpui/README.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/crates/gpui/README.md b/crates/gpui/README.md index 9b087a9752a05586b97a67962b20e86c953672ec..5278b024aedb8e1489e679da739e4d4fe7806fcc 100644 --- a/crates/gpui/README.md +++ b/crates/gpui/README.md @@ -15,7 +15,7 @@ Everything in GPUI starts with an `App`. You can create one with `App::new()`, a ## The Big Picture -GPUI offers three different registers(https://en.wikipedia.org/wiki/Register_(sociolinguistics)) depending on your needs: +GPUI offers three different [registers](https://en.wikipedia.org/wiki/Register_(sociolinguistics)) depending on your needs: - State management and communication with Models. Whenever you need to store application state that communicates between different parts of your application, you'll want to use GPUI's models. Models are owned by GPUI and are only accessible through an owned smart pointer similar to an `Rc`. See the `app::model_context` module for more information.