diff --git a/data/web/corefork.telegram.org/api/wallpapers.html b/data/web/corefork.telegram.org/api/wallpapers.html
index 2306b4ba95..8a75b583ee 100644
--- a/data/web/corefork.telegram.org/api/wallpapers.html
+++ b/data/web/corefork.telegram.org/api/wallpapers.html
@@ -157,12 +157,17 @@ If set, rotation
indicates clockwise rotation angle of the gradient
Once you've uploaded your wallpaper or received a wallpaper deep link, it can be installed as follows.
Note that fill wallpapers cannot be installed using the API, clients should install and keep track of them only locally, without synchronizing the wallpaper list or signalling installations.
The API keeps a list of wallpapers that the user can set as chat background, including some preinstalled ones.
-To fetch this list use account.getWallPapers.
-To save a wallpaper to that list use account.saveWallPaper with unsave=false
.
+To fetch the list use account.getWallPapers.
+To save a wallpaper to the list use account.saveWallPaper with unsave=false
.
To remove a wallpaper (including preinstalled wallpapers) from the list use account.saveWallPaper with unsave=true
.
To restore the default list, removing all installed wallpapers and reinstalling previously removed preinstalled wallpapers use account.resetWallPapers.
When a client sets a wallpaper as the default chat background, it should call account.installWallPaper to signal this installation to the server.
-In all cases where an InputWallPaper constructor is required, pass inputWallPaperSlug when working with wallpaper deep links and inputWallPaper otherwise, using the ID and access hash fields of a full wallPaper.
+When a client sets a wallpaper as the default chat background, call account.installWallPaper to signal this installation to the server.
+In all cases where an InputWallPaper constructor is required, pass:
+