From 6d17274fa1911e544c9bb2024026ce9a1f44c712 Mon Sep 17 00:00:00 2001
From: Bibo-Joshi <22366557+Bibo-Joshi@users.noreply.github.com>
Date: Wed, 6 Oct 2021 12:36:34 +0200
Subject: [PATCH] Updated Code snippets (markdown)

---
 Code-snippets.md | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)

diff --git a/Code-snippets.md b/Code-snippets.md
index 5821f25..578f959 100644
--- a/Code-snippets.md
+++ b/Code-snippets.md
@@ -150,7 +150,7 @@ To catch the incoming message with the location/contact, use `MessageHandler` wi
 ### Message Formatting (bold, italic, code, ...)
 
 Telegram supports some formatting options for text. All the details about what is supported can be found [here](https://core.telegram.org/bots/api#formatting-options).
-You can format text with every API method/type that has a `parse_mode` parameter. In addition to editing your text as described in the link above, pass one of the parse modes available through [`telegram.ParseMode`](https://python-telegram-bot.readthedocs.io/en/stable/telegram.parsemode.htm ) to the `parse_mode` parameter. Since th `5.0` update of the Bot API (version `13.1+` of PTB), you can alternatively pass a list of [`telegram.MessageEntities`](https://python-telegram-bot.readthedocs.io/en/stable/telegram.messageentity.html) to the `entities` parameter.
+You can format text with every API method/type that has a `parse_mode` parameter. In addition to editing your text as described in the link above, pass one of the parse modes available through [`telegram.ParseMode`](https://python-telegram-bot.readthedocs.io/en/stable/telegram.parsemode.html) to the `parse_mode` parameter. Since th `5.0` update of the Bot API (version `13.1+` of PTB), you can alternatively pass a list of [`telegram.MessageEntities`](https://python-telegram-bot.readthedocs.io/en/stable/telegram.messageentity.html) to the `entities` parameter.
 
 *Note:* In the API 4.5 update, Telegram introduced MarkdownV2, which supports nested entities and needs other escaping than v1. Markdown V1 is referred as legacy mode by the official API docs, and you should prefer MarkdownV2. Make sure to also use `reply_markdown_v2` instead of `reply_markdown` etc.