summaryrefslogtreecommitdiff
path: root/doc/it/weechat_user.it.adoc
diff options
context:
space:
mode:
authorSébastien Helleu <flashcode@flashtux.org>2021-12-04 15:46:22 +0100
committerSébastien Helleu <flashcode@flashtux.org>2021-12-04 15:59:46 +0100
commit50cea48b51a776ab68e6feb455de730aec9d309a (patch)
tree87719e64238b7ad461400a6f138e295bd9a3d8e4 /doc/it/weechat_user.it.adoc
parentae891ab3229d81558615555bf0dc1eb8f90b3ac8 (diff)
downloadweechat-50cea48b51a776ab68e6feb455de730aec9d309a.zip
doc: move section "Upgrade" at top level after "Installation" (user's guide)
Diffstat (limited to 'doc/it/weechat_user.it.adoc')
-rw-r--r--doc/it/weechat_user.it.adoc10
1 files changed, 5 insertions, 5 deletions
diff --git a/doc/it/weechat_user.it.adoc b/doc/it/weechat_user.it.adoc
index 78264a8c3..c74c44a0c 100644
--- a/doc/it/weechat_user.it.adoc
+++ b/doc/it/weechat_user.it.adoc
@@ -581,7 +581,7 @@ Poi, come per un crash, usare il comando `bt full`:
// TRANSLATION MISSING
[[upgrade]]
-=== Upgrade
+== Upgrade
If a new stable version of WeeChat is released, this is time for you to
switch to this version.
@@ -593,7 +593,7 @@ This can be done while WeeChat is running.
// TRANSLATION MISSING
[[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
@@ -619,10 +619,10 @@ $ weechat --upgrade
// TRANSLATION MISSING
[[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]
@@ -635,7 +635,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`):