summaryrefslogtreecommitdiffstats
diff options
context:
space:
mode:
authorintrigeri <intrigeri@boum.org>2016-05-21 15:19:57 +0000
committerintrigeri <intrigeri@boum.org>2016-05-21 15:19:57 +0000
commit297a0f1a829bda7ffae16387480953f746779c5d (patch)
tree7f6068a1a9c5fab8a6df9116fe85d02edc0d2e2a
parent0c8fb488e1ee09bb00b2fe39a9977bf2d598dba7 (diff)
Fix phrasing.
-rw-r--r--wiki/src/contribute/APT_repository/time-based_snapshots.mdwn6
1 files changed, 3 insertions, 3 deletions
diff --git a/wiki/src/contribute/APT_repository/time-based_snapshots.mdwn b/wiki/src/contribute/APT_repository/time-based_snapshots.mdwn
index 7942de1..bbf60d8 100644
--- a/wiki/src/contribute/APT_repository/time-based_snapshots.mdwn
+++ b/wiki/src/contribute/APT_repository/time-based_snapshots.mdwn
@@ -318,8 +318,8 @@ situation here is mostly:
To grant a freeze exception to a given package, we simply import it
into our own
[[custom APT repository|contribute/APT repository/custom]], in the
-suite corresponding to the branch that we want to see this package ⇒
-in the general case, the upgraded package will be installed in the
+suite corresponding to the branch that we want to see this package in
+⇒ in the general case, the upgraded package will be installed in the
next Tails release.
This works because our APT pinning ranks Tails custom APT suites at
@@ -354,7 +354,7 @@ numbers):
1. Import the package we want to upgrade into our own
[[custom APT repository|contribute/APT repository/custom]], in
the suite corresponding to the branch that we want to see this
- package.
+ package in.
2. Explicitly pin, in `config/chroot_apt/preferences`, the upgraded
package we have just imported to a value higher than 990, with