From b6ca39b88e03ae364dae4dff0595c01aa5d5ba15 Mon Sep 17 00:00:00 2001
From: Daniil Gentili <daniil@daniil.it>
Date: Wed, 5 Jun 2019 10:51:09 +0200
Subject: [PATCH] Resetstate docs

---
 docs/docs/UPDATES.md | 10 +++++++++-
 1 file changed, 9 insertions(+), 1 deletion(-)

diff --git a/docs/docs/UPDATES.md b/docs/docs/UPDATES.md
index d1896553..48dcb7f1 100644
--- a/docs/docs/UPDATES.md
+++ b/docs/docs/UPDATES.md
@@ -11,7 +11,7 @@ Update handling can be done in different ways:
 * [Multi-account: Async Combined Event driven update handling](#async-combined-event-driven)
 * [Async Callback](#async-callback)
 * [Noop (default)](#noop)
-
+* [Fetch all updates from the beginning](#fetch-all-updates-from-the-beginning)
 
 ```
 
@@ -246,4 +246,12 @@ $MadelineProto->setNoop();
 When an [Update](https://docs.madelineproto.xyz/API_docs/types/Update.html) is received, nothing is done. This is useful if you need to populate the internal peer database with peers to avoid `This peer is not present in the internal peer database errors`, but don't need to handle updates.  
 This is the default.  
 
+
+## Fetch all updates from the beginning
+
+You can use the `resetUpdateState` method to reset the update state and fetch all updates from the beginning:  
+```php
+$MadelineProto->resetUpdateState();
+```
+
 <a href="https://docs.madelineproto.xyz/docs/SETTINGS.html">Next section</a>
\ No newline at end of file