From 129a4ca022208ebf4a5c31f96a6564572846211c Mon Sep 17 00:00:00 2001
From: Ian Grigg <iang@cacert.org>
Date: Fri, 13 Mar 2009 19:43:22 +0000
Subject: [PATCH] heading numbering only

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

diff --git a/SecurityPolicy.html b/SecurityPolicy.html
index 2ef4e87..9b69ed1 100644
--- a/SecurityPolicy.html
+++ b/SecurityPolicy.html
@@ -721,13 +721,13 @@ The standard of monitoring, alerting and reporting must be documented.
 </p>
 
 <h3> <a name="5.3">5.3.</a> Immediate Action </h3>
-<h4> <a name="5.2.1">5.2.1.</a> Severity and Priority </h4>
+<h4> <a name="5.3.1">5.3.1.</a> Severity and Priority </h4>
 <p>
 On discovery of an incident,
 an initial assessment of severity and priority must be made.
 </p>
 
-<h4> <a name="5.2.2">5.2.2.</a> Communications </h4>
+<h4> <a name="5.3.2">5.3.2.</a> Communications </h4>
 <p>
 An initial report should be circulated.
 </p>
@@ -737,7 +737,7 @@ A communications forum should be established for direct
 support of high priority or high severity incidents.
 </p>
 
-<h4> <a name="5.2.3">5.2.3.</a> Escalation </h4>
+<h4> <a name="5.3.3">5.3.3.</a> Escalation </h4>
 <p>
 A process of escalation should be established
 for oversight and management purposes,