diff options
authorintrigeri <>2015-10-22 13:56:00 +0000
committerintrigeri <>2015-10-22 13:56:00 +0000
commitff8167afa87b27edb8f690560eca98e15ec66d48 (patch)
parent3f2c5ea3569eb35cba3a9bb369080a40984bde0a (diff)
Fix typos.
1 files changed, 3 insertions, 3 deletions
diff --git a/wiki/src/blueprint/freezable_APT_repository.mdwn b/wiki/src/blueprint/freezable_APT_repository.mdwn
index fa37051..9256051 100644
--- a/wiki/src/blueprint/freezable_APT_repository.mdwn
+++ b/wiki/src/blueprint/freezable_APT_repository.mdwn
@@ -6,8 +6,8 @@ This is about [[!tails_ticket 5926]].
A given APT repository snapshot is immutable after it's been taken.
If we need a freeze exception, we can import the specific package we
-want into a Tails -specific APT suite, use it until the next Tails
-release, and ensure it's removed from the Tails -specific APT suite
+want into a Tails-specific APT suite, use it until the next Tails
+release, and ensure it's removed from the Tails-specific APT suite
later, when appropriate.
We want to have reproducible builds some day. Therefore, the APT
@@ -86,7 +86,7 @@ except:
## APT sources used inside Tails
A running Tails' APT must be pointed at the official, live Debian
-archive, and not to a Tails -specific and already obsolete snapshot.
+archive, and not to a Tails-specific and already obsolete snapshot.
To achieve that we can tweak `sources.list` as we already do in
[[!tails_gitweb config/chroot_local-includes/lib/live/config/1500-reconfigure-APT]].