From 720c8b2c5f92ebb26240ec7e6610b7f63707ff1a Mon Sep 17 00:00:00 2001 From: =?UTF-8?q?=D0=A1=D1=8B=D1=80=D1=86=D0=B5=D0=B2=20=D0=92=D0=B0=D0=B4?= =?UTF-8?q?=D0=B8=D0=BC=20=D0=98=D0=B3=D0=BE=D1=80=D0=B5=D0=B2=D0=B8=D1=87?= Date: Wed, 10 Jan 2024 13:44:33 +0300 Subject: [PATCH] Fix docs styling --- crates/teloxide/src/lib.rs | 26 +++++++++++++------------- 1 file changed, 13 insertions(+), 13 deletions(-) diff --git a/crates/teloxide/src/lib.rs b/crates/teloxide/src/lib.rs index b5a4176d..836138c2 100644 --- a/crates/teloxide/src/lib.rs +++ b/crates/teloxide/src/lib.rs @@ -39,15 +39,15 @@ //! //! There is a great number of [update kinds] and [message kinds] to work with! //! Usually it's essential to filter specific ones and process them in `handler -//! functions`. Teloxide provides some `filter methods` for [Update] and -//! [Message] types in [UpdateFilterExt] and [MessageFilterExt] traits +//! functions`. Teloxide provides some `filter methods` for [`Update`] and +//! [`Message`] types in [`UpdateFilterExt`] and [`MessageFilterExt`] traits //! respectively. In addition to filtering, these methods will `inject` the //! appropriate type into your handler functions. For instance, if you use -//! [Update::filter_message], the instance of the [Message] will be available as -//! a parameter for your handler functions. Similarly the use of -//! [Message::filter_text] will inject a [String] into the context. +//! [`Update::filter_message`], the instance of the [`Message`] will be +//! available as a parameter for your handler functions. Similarly the use of +//! [`Message::filter_text`] will inject a [`String`] into the context. //! -//! Moreover, [filter_map] function can inject some dependencies according to +//! Moreover, [`filter_map`] function can inject some dependencies according to //! the schema flow. More in the example below! //! //! Here is a quick example (filter text message and inject it's text into the @@ -96,13 +96,13 @@ //! //! [update kinds]: crate::types::UpdateKind //! [message kinds]: crate::types::MessageKind -//! [Update]: crate::types::Update -//! [Message]: crate::types::Message -//! [Message::filter_text]: crate::dispatching::MessageFilterExt::filter_text -//! [UpdateFilterExt]: crate::dispatching::MessageFilterExt -//! [MessageFilterExt]: crate::dispatching::UpdateFilterExt -//! [Update::filter_message]: crate::dispatching::UpdateFilterExt::filter_message -//! [filter_map]: crate::prelude::Handler::filter_map +//! [`Update`]: crate::types::Update +//! [`Message`]: crate::types::Message +//! [`Message::filter_text`]: crate::dispatching::MessageFilterExt::filter_text +//! [`UpdateFilterExt`]: crate::dispatching::UpdateFilterExt +//! [`MessageFilterExt`]: crate::dispatching::MessageFilterExt +//! [`Update::filter_message`]: crate::dispatching::UpdateFilterExt::filter_message +//! [`filter_map`]: crate::prelude::Handler::filter_map // This hack is used to cancel formatting for a Markdown table. See [1], [2], and [3]. //