From b569fede4a119fb52f8a45c54ab0592f827fa61e Mon Sep 17 00:00:00 2001 From: sajolida Date: Thu, 10 Jan 2019 18:31:02 +0000 Subject: [PATCH] Style guide: update vs upgrade --- .../contribute/how/documentation/style_guide.mdwn | 21 +++++++++++++++++++++ 1 file changed, 21 insertions(+) diff --git a/wiki/src/contribute/how/documentation/style_guide.mdwn b/wiki/src/contribute/how/documentation/style_guide.mdwn index 53ff9e8b912..f15ba81f72e 100644 --- a/wiki/src/contribute/how/documentation/style_guide.mdwn +++ b/wiki/src/contribute/how/documentation/style_guide.mdwn @@ -164,6 +164,27 @@ Without an article. Not *the Greeter*. Note the formatting as an application. +- **update** vs **upgrade** + + - Use **upgrade** to refer to the replacement of a previous version of + Tails by another. + + - *For example:* + + - If you know someone you trust who already did the upgrade, you can + upgrade your Tails by cloning from their Tails.

+ + - You might use **update** to refer to other operations that update + some data or software outside of Tails releases. + + - *For example:* + + - Make sure to update your *dotfiles* each time you use the **init** + command of *keyringer*. + + - The packages from your list of additional software will be updated + automatically when you connect to the Internet. + - **vulnerability** or **security vulnerability** And not *hole* or *issue*. -- 2.11.4.GIT