Updated BotApp to GatewayBot.
@@ -51,17 +51,17 @@ writing their first bot in other frameworks simply because of working blind afte
to set up standard logging messages.
If you wish to customise the intents being used in order to change which events your bot is notified about, then you
-can pass the `intents` kwarg to the `BotApp` constructor:
+can pass the `intents` kwarg to the `GatewayBot` constructor:
```py
# the default is to enable all unprivileged intents (all events that do not target the
# presence or activity of a specific member).
-bot = hikari.BotApp(intents=hikari.Intents.ALL, token="...")
+bot = hikari.GatewayBot(intents=hikari.Intents.ALL, token="...")
```
The above example would enable all intents, thus enabling events relating to member presences to be received
(you'd need to whitelist your application first to be able to start the bot if you do this).
-[Other options also exist](https://hikari-py.github.io/hikari/hikari/impl/bot.html#hikari.impl.bot.BotApp) such as
+[Other options also exist](https://hikari-py.github.io/hikari/hikari/impl/bot.html#hikari.impl.bot.GatewayBot) such as
[customising timeouts for requests](https://hikari-py.github.io/hikari/hikari/config.html#hikari.config.HTTPSettings.timeouts)
and [enabling a proxy](https://hikari-py.github.io/hikari/hikari/config.html#hikari.config.ProxySettings).
@@ -78,7 +78,7 @@ bot.run(
)
```
-[Many other helpful options](https://hikari-py.github.io/hikari/hikari/impl/bot.html#hikari.impl.bot.BotApp.run)
+[Many other helpful options](https://hikari-py.github.io/hikari/hikari/impl/bot.html#hikari.impl.bot.GatewayBot.run)
exist for you to take advantage of if you wish.
Events are determined by the type annotation on the event parameter, or alternatively as a type passed to the
@@ -179,7 +179,7 @@ if os.name != "nt":
import uvloop
uvloop.install()
-bot = hikari.BotApp(...)
+bot = hikari.GatewayBot(...)
...
```
