From 7fea4e265f9e16f3eb2776be627193930be1d3e2 Mon Sep 17 00:00:00 2001 From: Lonami Exo Date: Thu, 22 Feb 2018 14:05:11 +0100 Subject: [PATCH] 80 characters --- readthedocs/extra/basic/entities.rst | 10 +++++----- 1 file changed, 5 insertions(+), 5 deletions(-) diff --git a/readthedocs/extra/basic/entities.rst b/readthedocs/extra/basic/entities.rst index d541366b..b68a74d7 100644 --- a/readthedocs/extra/basic/entities.rst +++ b/readthedocs/extra/basic/entities.rst @@ -67,11 +67,11 @@ Entities vs. Input Entities On top of the normal types, the API also make use of what they call their -``Input*`` versions of objects. -The input version of an entity (e.g. ``InputPeerUser``, ``InputChat``, -etc.) only contains the minimum information that's required from Telegram -to be able to identify who you're referring to: -a Peer's **ID** and **hash**. +``Input*`` versions of objects. The input version of an entity (e.g. +``InputPeerUser``, ``InputChat``, etc.) only contains the minimum +information that's required from Telegram to be able to identify +who you're referring to: a ``Peer``'s **ID** and **hash**. + This ID/hash pair is unique per user, so if you use the pair given by another user **or bot** it will **not** work.