From f4f421fe1a8b484b85e3330fe3be7887230b7df3 Mon Sep 17 00:00:00 2001
From: Ulrich Schroeter <ulrich@cacert.org>
Date: Sat, 23 Feb 2013 15:33:04 +0000
Subject: [PATCH] after clarification what [cacert-policy] is meant (Policy
 Group was meant by CCS work) added section 0, 1 minor fixes

git-svn-id: http://svn.cacert.org/CAcert/Policies@2458 14b1bab8-4ef6-0310-b690-991c95c89dfd
---
 PolicyOnPolicy.html | 4 ++--
 1 file changed, 2 insertions(+), 2 deletions(-)

diff --git a/PolicyOnPolicy.html b/PolicyOnPolicy.html
index 497b36e..b71c413 100644
--- a/PolicyOnPolicy.html
+++ b/PolicyOnPolicy.html
@@ -83,7 +83,7 @@ Licence: <a style="color: steelblue" href="//wiki.cacert.org/Policy#Licence" tit
 <p>
     Policy on Policy adopts the IETF model of
     'rough consensus' to create CAcert documents
-    within the open [<span class="change">cacert-</span>policy] mail list forum.
+    within the open <span class="strike">[policy] mail list forum.</span> <span class="change">CAcert Policy Group <a href="https://lists.cacert.org/wws/info/cacert-policy"> mail list forum</a></span>.
 </p>
 
 
@@ -118,7 +118,7 @@ The policies so created are generally binding on
 The Policy Officer manages all policies
 and the policy group.
 The policy group is formed on the open mailing list
-known as [<span class="change">cacert-</span>policy], and is to be open to all
+known as <span class="strike">[cacert-policy]</span> <span class="change">CAcert Policy Group</span>, and is to be open to all
 Community Members of CAcert.
 </p>