Tails

#1 Updated by sajolida 2017-09-11 10:43:47

• Target version changed from Tails_3.2 to Tails_3.3

#2 Updated by sajolida 2017-11-14 13:23:15

• Target version changed from Tails_3.3 to Tails_3.5

#3 Updated by sajolida 2017-12-28 01:00:27

• related to Feature #15130: Restructure our support page and content added

#4 Updated by anonym 2018-01-23 19:52:50

• Target version changed from Tails_3.5 to Tails_3.6

#5 Updated by sajolida 2018-02-23 17:54:57

• Assignee changed from sajolida to cbrownstein
• Parent task set to Feature #15130
• QA Check set to Ready for QA
• Feature Branch set to doc/14533-known-issues-vs-faq

Cody: Do you want to have a look?

This ticket was created before Feature #15130 but it’s really a part of the same effort.

I’m not explaining on each page what the page itself is about because it felt dumb. People will see that quickly from the table of content I think. I’m only explaining what other pages are about.

#6 Updated by cbrownstein 2018-02-25 03:14:38

• Assignee changed from cbrownstein to sajolida
• QA Check changed from Ready for QA to Pass

Looks good. However, I have one nitpicky suggestion that can freely be disregarded:

/support/known_issues.mdwn

Instead of “For more generic questions about Tails…” say, “For more general questions about Tails….”

“Generic” → “not unique.” For example, rebooting is a generic way to fix many computer problems.
“General” → “not specific.” For example, as a general rule, one should not assume that an unencrypted email cannot be read by others.

I think by definition, a FAQ contains unique questions; but might not contain the answer to a specific question.

Again, nitpicky. :-)

#7 Updated by sajolida 2018-03-08 11:29:12

• Status changed from Confirmed to Resolved
• Assignee deleted (sajolida)

Thanks for the fix. These are the things that are especially challenging for me as I’m not a native speaker.

I applied your fix and merged.