From 4ab05a025f424c0b5ce140ff68182e20595b04a2 Mon Sep 17 00:00:00 2001
From: Luke Shumaker <LukeShu@sbcglobal.net>
Date: Fri, 19 Apr 2013 19:11:04 -0400
Subject: manually replace more instances of the Arch name

---
 templates/public/keys.html | 4 ++--
 1 file changed, 2 insertions(+), 2 deletions(-)

(limited to 'templates/public/keys.html')

diff --git a/templates/public/keys.html b/templates/public/keys.html
index 1a21827a..4afc6d6b 100644
--- a/templates/public/keys.html
+++ b/templates/public/keys.html
@@ -8,7 +8,7 @@
 <div id="signing-keys" class="box">
     <h2>Master Signing Keys</h2>
 
-    <p>This page lists the Arch Linux Master Keys. This is a distributed set of
+    <p>This page lists the {{ BRANDING_DISTORNAME }} Master Keys. This is a distributed set of
     keys that are seen as "official" signing keys of the distribution. Each key
     is held by a different developer, and a revocation certificate for the key
     is held by a different developer. Thus, no one developer has absolute hold
@@ -53,7 +53,7 @@
     personal key of the developer is signed by the given master key. A 'No'
     indicates it has not been signed; however, this does not necessarily mean
     the key should not be trusted.</p>
-    <p>All official Arch Linux developers and trusted users should have their
+    <p>All official {{ BRANDING_DISTRONAME }} developers and trusted users should have their
     key signed by at least three master keys if they are responsible for
     packaging software in the repositories. This is in accordance with the PGP
     <em>web of trust</em> concept. If a user is willing to marginally trust all
-- 
cgit v1.2.3