From 7ae19a964f67f5b67ac80d43daf95a9bab1d5291 Mon Sep 17 00:00:00 2001
From: kurkuruzo <65871180+kurkuruzo@users.noreply.github.com>
Date: Mon, 20 Mar 2023 12:18:45 +0300
Subject: [PATCH] Corrected a link to "Making your bot persistent" page

---
 Arbitrary-callback_data.md | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)

diff --git a/Arbitrary-callback_data.md b/Arbitrary-callback_data.md
index 99ca56a..595f034 100644
--- a/Arbitrary-callback_data.md
+++ b/Arbitrary-callback_data.md
@@ -6,7 +6,7 @@ With PTB, you are able to pass *any* object as `callback_data`. This is achieved
 
 This means two things for you:
 
-1. If you don't use [persistence](../Making-your-bot-persistent), buttons won't work after restarting your bot, as the stored updates are lost. More precisely, the `callback_data` you will receive is an instance of  `telegram.ext.InvalidCallbackData`. If you don't need persistence otherwise, you can set `store_callback_data` to `True` and all the others to `False`.
+1. If you don't use [persistence](../wiki/Making-your-bot-persistent), buttons won't work after restarting your bot, as the stored updates are lost. More precisely, the `callback_data` you will receive is an instance of  `telegram.ext.InvalidCallbackData`. If you don't need persistence otherwise, you can set `store_callback_data` to `True` and all the others to `False`.
 2. If you have a number of keyboards that need to stay valid for a very long time, you might need to do some tweaking manually (see below)
 3. When using the `CallbackQueryHandler`, the `pattern` argument can now be either