From b68bcf9cff85bf8deab721ae7b779eb54b4cd8e2 Mon Sep 17 00:00:00 2001 From: Johannes Marbach Date: Sun, 25 Feb 2024 10:49:33 +0100 Subject: [PATCH] fix(examples): Fix typos in getting started example Signed-off-by: Johannes Marbach --- examples/getting_started/src/main.rs | 6 +++--- 1 file changed, 3 insertions(+), 3 deletions(-) diff --git a/examples/getting_started/src/main.rs b/examples/getting_started/src/main.rs index 47efa0344..2e6d94387 100644 --- a/examples/getting_started/src/main.rs +++ b/examples/getting_started/src/main.rs @@ -40,7 +40,7 @@ async fn main() -> anyhow::Result<()> { "Usage: {} ", env::args().next().unwrap() ); - // exist if missing + // exit if missing exit(1) } }; @@ -143,8 +143,8 @@ async fn on_stripped_state_member( // This fn is called whenever we see a new room message event. You notice that // the difference between this and the other function that we've given to the // handler lies only in their input parameters. However, that is enough for the -// rust-sdk to figure out which one to call one and only do so, when -// the parameters are available. +// rust-sdk to figure out which one to call and only do so, when the parameters +// are available. async fn on_room_message(event: OriginalSyncRoomMessageEvent, room: Room) { // First, we need to unpack the message: We only want messages from rooms we are // still in and that are regular text messages - ignoring everything else.