diff --git a/data/web/corefork.telegram.org/api/ringtones.html b/data/web/corefork.telegram.org/api/ringtones.html index cffea4413c..19511a7603 100644 --- a/data/web/corefork.telegram.org/api/ringtones.html +++ b/data/web/corefork.telegram.org/api/ringtones.html @@ -70,9 +70,9 @@ After upload, the document should be provided to account.saveRingtone and an account.savedRingtoneConverted constructor will be returned containing the new document to use instead of the one returned by account.uploadRingtone when removing or using notification sounds.

The following ringtone limits are specified in the client configuration:

Removing notification sounds

Schema:

@@ -92,7 +92,8 @@ After upload, the document should be provided to account.getSavedRingtones can be used to obtain all saved notification sounds: the client will receive updateSavedRingtones updates if the list is modified by the user on other clients.

+

account.getSavedRingtones can be used to obtain all saved notification sounds.
+The client will receive an updateSavedRingtones update if the list is modified by the user on other clients, which should trigger a call to account.getSavedRingtones.

Setting notification sounds

Schema:

notificationSoundDefault#97e8bebe = NotificationSound;
@@ -110,7 +111,7 @@ After upload, the document should be provided to account.updateNotifySettings, populating the ios_sound, android_sound or other_sound fields according to the platform where a sound should be played.  

+

To set the notification sound to play when receiving messages from a specific peer or from a category of peers, use account.updateNotifySettings, populating the ios_sound, android_sound or other_sound fields according to the platform where the sound should be played.

The fields can be populated with the following constructors: