summaryrefslogtreecommitdiffstats
path: root/wiki/src/blueprint/bootstrapping/installer.mdwn
diff options
context:
space:
mode:
Diffstat (limited to 'wiki/src/blueprint/bootstrapping/installer.mdwn')
-rw-r--r--wiki/src/blueprint/bootstrapping/installer.mdwn22
1 files changed, 11 insertions, 11 deletions
diff --git a/wiki/src/blueprint/bootstrapping/installer.mdwn b/wiki/src/blueprint/bootstrapping/installer.mdwn
index e590eb0..4a02122 100644
--- a/wiki/src/blueprint/bootstrapping/installer.mdwn
+++ b/wiki/src/blueprint/bootstrapping/installer.mdwn
@@ -16,7 +16,7 @@ requires having two USB sticks and going through manual installation
steps, often using command line.
We want to eliminate the need for a first temporary Tails and have Tails
-Installer available on Linux, Windows, and Mac OS.
+Installer available on Linux, Windows, and macOS.
As part of the ISO verification process we also want to push more
verification logic to Tails Installer. See the [[blueprint on ISO
@@ -34,8 +34,8 @@ Roadmap
----
In 2015 we will work on porting Tails Installer to Debian. This is a
-first step before having Tails available on any other platform.
-This requires rethinking the scenarios in which Tails Installer is
+first step before having Tails available on any other platform.
+This requires rethinking the scenarios in which Tails Installer is
used ([[!tails_ticket 7046]]) and adapting its interface accordingly.
Those are the improvements that we propose for 2015:
@@ -67,22 +67,22 @@ First of all:
2. Simplify the splash screen a bit thanks to the autodetection code:
merge "Clone and Install" and "Clone and Upgrade" into one single
"Clone" button: Depending on whether the destination device already
- has Tails installed or not, dynamically change the label of main
+ has Tails installed or not, dynamically change the label of main
action button to "Install" or "Upgrade" (for the second device).
- (Note: this breaks the "re-installing Tails from scratch" use case,
- but IIRC we already have documented how to uninstall Tails, so that's
+ (Note: this breaks the "re-installing Tails from scratch" use case,
+ but IIRC we already have documented how to uninstall Tails, so that's
no big deal). ([[!tails_ticket 9006]])
3. If the destination device already has Tails installed, add a second
- button below or side-by-side with the "Install" button with the label
- "Upgrade". This allows to choose once more to either reinstall Tails
+ button below or side-by-side with the "Install" button with the label
+ "Upgrade". This allows to choose once more to either reinstall Tails
from scratch or to upgrade the exisiting installation.
4. When using the installer in Tails (as opposed to using the installer
- from another platform), remove the splash screen and add a "Clone"
+ from another platform), remove the splash screen and add a "Clone"
button to the main interface. ([[!tails_ticket 8859]])
And then:
-- If using the installer outside of Tails, point to the website to
+- If using the installer outside of Tails, point to the website to
download the ISO. ([[!tails_ticket 8867]])
- Make it possible to "Upgrade from ISO" from
the command line. See the [[Debian Hacker|bootstrapping#tools]] bootstrapping path. ([[!tails_ticket 8861]])
@@ -90,7 +90,7 @@ And then:
the command line. See the [[Debian Hacker|bootstrapping#tools]] bootstrapping path. ([[!tails_ticket 8861]]).
- Store version of Tails on destination key after install and upgrade. ([[!tails_ticket 8863]])
- This would allow to display version in "Target Device". ([[!tails_ticket 8862]])
-- Have Tails Installer available on Mac OS as there is currently no suitable other
+- Have Tails Installer available on macOS as there is currently no suitable other
installation technique using a graphical interface.
Future