None
Source string added |
|
None
Source string added |
|
None
Source string added |
|
None
Source string added |
|
None
Source string added |
|
None
Source string added |
|
None
Source string added |
|
None
Source string added |
|
None
Source string added |
|
None
Source string added |
|
None
Source string added |
|
None
Source string added |
|
None
Source string added |
|
None
Source string added |
|
sajolida
Comment resolved |
Comment resolved
11 months ago
|
sajolida
Comment resolved |
Comment resolved
11 months ago
|
sajolida
Comment added |
It's common in technical writing to capitalize the name of products or important features. That's why we write "Persistent Storage" and not "persistent storage": https://tails.net/contribute/how/documentation/style_guide/#persistent-storage. There are some debates about what deserves capitalization or not within the industry, though: https://www.reddit.com/r/ProductManagement/comments/mqjth3/arguments_for_and_against_capitalizing_feature/. So, I think that what matters here is consistency and we've capitalized the Welcome Screen until now. 11 months ago |
None
Source string added |
|
None
Source string added |
|
None
Source string added |
|
<p class="code mac">https://tails.net/install/mac?back=1</p>
<p class="code linux">https://tails.net/install/linux?back=1</p>
<p class="code expert">https://tails.net/install/expert?back=1</p>
<p class="code pc-clone">https://tails.net/install/clone/pc?back=1</p>
<p class="code mac-clone">https://tails.net/install/clone/mac?back=1</p>
<p class="code upgrade-tails">https://tails.net/doc/upgrade/tails?back=1</p>
<p class="code upgrade-windows">https://tails.net/doc/upgrade/windows?back=1</p>
<p class="code upgrade-mac">https://tails.net/doc/upgrade/mac?back=1</p>
<p class="code upgrade-linux">https://tails.net/doc/upgrade/linux?back=1</p>
<p class="code upgrade-clone">https://tails.net/doc/upgrade/clone?back=1</p>