diff --git a/data/web/corefork.telegram.org/api/giveaways.html b/data/web/corefork.telegram.org/api/giveaways.html
index 9e52cc92c1..37a20d850c 100644
--- a/data/web/corefork.telegram.org/api/giveaways.html
+++ b/data/web/corefork.telegram.org/api/giveaways.html
@@ -156,8 +156,8 @@ Another way for admins to check who received the gifts is to simply use The stars
, currency
and amount
from the chosen starsGiveawayOption and some extra options, as specified in the constructor page ».
additional_peers
. countries_iso2
. until_date
, and it must be at most giveaway_period_max seconds in the future; at that date, Telegram will randomly choose option.users
subscribers according to the conditions specified above, and send them a Telegram Premium giftcode as a messageActionGiftCode constructor, that should be used client-side to generate a giftcode link. boost_peer
will receive giveaway_boosts_per_premium boosts from each user, that cannot be reassigned to another channel/supergroup for the duration of the gifted subscription. until_date
, and it must be at most giveaway_period_max seconds in the future; at that date, Telegram will randomly choose users
subscribers according to the conditions specified above, and send them per_user_stars
Telegram Stars as a messageActionPrizeStars constructor. boost_peer
will receive starsGiveawayOption boosts from each user, that cannot be reassigned to another channel/supergroup for the duration of the gifted subscription. Then, follow the invoice payment flow as described in the payments documentation ».
More alternative payment flows are also available:
diff --git a/data/web/corefork.telegram.org/api/layers.html b/data/web/corefork.telegram.org/api/layers.html index d14a03a216..83a43509a4 100644 --- a/data/web/corefork.telegram.org/api/layers.html +++ b/data/web/corefork.telegram.org/api/layers.html @@ -199,7 +199,7 @@