2. Users
3. sajolida

Actually, I think that https://tails.net/doc/first_steps/reset/linux/ did not follow these rules. Fixed with c419eae445a.

2 weeks ago

I checked git grep Disks -- "*.*m*" and I think that we're consistent already:

• We're writing "the Disks utility" when people are already in Tails
• We're writing GNOME Disks when people are on their Linux system, because they might or might not have GNOME

The page https://tails.net/doc/upgrade/tails/ is a bit of an exception, but we're writing GNOME Disks there to be consistent within the document.

Anything that doesn't follow these rules?

2 weeks ago

Sure. Added to the list of updates for https://gitlab.tails.boum.org/tails/tails/-/issues/20203.

a month ago

Comment resolved 11 months ago

Comment resolved a year ago

Comment resolved a year ago

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.

a year ago

Comment resolved a year ago

Comment resolved a year ago

Comment resolved a year ago