From 92fcb5181f754230b3f9cbfffed1689113f1d119 Mon Sep 17 00:00:00 2001 From: Jimmy Cuadra Date: Sun, 2 Jun 2019 04:13:08 -0700 Subject: [PATCH] Fix typos. --- src/lib.rs | 2 +- src/stripped.rs | 2 +- 2 files changed, 2 insertions(+), 2 deletions(-) diff --git a/src/lib.rs b/src/lib.rs index 38e3ec4c..488dec66 100644 --- a/src/lib.rs +++ b/src/lib.rs @@ -67,7 +67,7 @@ //! //! Although any Rust type that implements `Event`, `RoomEvent`, or `StateEvent` can serve as a //! Matrix event type, ruma_events also includes a few convenience types for representing events -//! that are not convered by the spec and not otherwise known by the application. +//! that are not covered by the spec and not otherwise known by the application. //! `CustomEvent`, `CustomRoomEvent`, and `CustomStateEvent` are simple implementations of their //! respective event traits whose `content` field is simply a `serde_json::Value` value, which //! represents arbitrary JSON. diff --git a/src/stripped.rs b/src/stripped.rs index f640a01e..e4e669a7 100644 --- a/src/stripped.rs +++ b/src/stripped.rs @@ -1,7 +1,7 @@ //! "Stripped-down" versions of the core state events. //! //! Each "stripped" event includes only the `content`, `type`, and `state_key` fields of its full -//! version. These stripped types are useful for APIs where the a is providing the content of a +//! version. These stripped types are useful for APIs where the user is providing the content of a //! state event to be created, when the other fields can be inferred from a larger context, or where //! the other fields are otherwise inapplicable.