summaryrefslogtreecommitdiff
path: root/doc/en/weechat_user.en.adoc
diff options
context:
space:
mode:
Diffstat (limited to 'doc/en/weechat_user.en.adoc')
-rw-r--r--doc/en/weechat_user.en.adoc10
1 files changed, 5 insertions, 5 deletions
diff --git a/doc/en/weechat_user.en.adoc b/doc/en/weechat_user.en.adoc
index b5a9cfd73..bf1ac5be6 100644
--- a/doc/en/weechat_user.en.adoc
+++ b/doc/en/weechat_user.en.adoc
@@ -523,7 +523,7 @@ Then like for a crash, use command `bt full`:
----
[[upgrade]]
-=== Upgrade
+== Upgrade
If a new stable version of WeeChat is released, this is time for you to
switch to this version.
@@ -534,7 +534,7 @@ required files are in the same paths. +
This can be done while WeeChat is running.
[[upgrade_command]]
-==== Upgrade command
+=== Upgrade command
WeeChat can restart the new binary, in place, using the
<<command_weechat_upgrade,/upgrade>> command: the buffer contents and non-SSL
@@ -559,10 +559,10 @@ $ weechat --upgrade
----
[[restart_after_upgrade]]
-==== Restart after upgrade
+=== Restart after upgrade
[[restart_release_notes]]
-===== Release notes
+==== Release notes
After an upgrade, it is *strongly recommended* to read the
https://weechat.org/files/releasenotes/ReleaseNotes-devel.html[release notes]
@@ -575,7 +575,7 @@ For example if you switch from version 3.0 to 3.2, you must read release notes
of versions 3.1 and 3.2.
[[restart_configuration_upgrade]]
-===== Configuration upgrade
+==== Configuration upgrade
WeeChat has an automatic upgrade of configuration files (`*.conf`):