Use formal name for the Eclipse Planning Council
The formal name includes the word "Eclipse". Further, "Eclipse Planning
Council" should always be capitalized.
diff --git a/policy_2011.php b/policy_2011.php
index 0db3a25..9e66e3c 100755
--- a/policy_2011.php
+++ b/policy_2011.php
@@ -42,16 +42,16 @@
<p>The document uses the ISO 27005 definition of vulnerability:
"A weakness of an asset or group of assets that can be exploited
by one or more threats."
- </p>
+ </p>
This document uses terms from the <a
href="http://www.eclipse.org/projects/dev_process/development_process.php"
class="external text"
title="http://www.eclipse.org/projects/dev_process/development_process.php"
rel="nofollow">Eclipse Development Process</a>.
</p>
-
+
<a name="Eclipse_Security_Team"></a>
-
+
<h2>Eclipse Security Team</h2>
<p>The Security Team is the first line of defense: it is effectively a
triage unit with security expertise. Ultimately, Vulnerabilities are
@@ -114,10 +114,10 @@
be made available to the community.</p>
<p>At a minimum, updated software is made available via normal project
distribution channels (e.g. downloads and update sites).</p>
- <p>The planning council must be made aware of Vulnerabilities in
- software that is part of the simultaneous release. The Planning
+ <p>The Eclipse Planning Council must be made aware of Vulnerabilities in
+ software that is part of the simultaneous release. The Eclipse Planning
Council will determine whether or not a "respin" of the simultaneous
- release repository and EPP packages is required. The Planning Council
+ release repository and EPP packages is required. The Eclipse Planning Council
will coordinate the timing of the "respin" with the Project
Leadership.</p>
<a name="Disclosure"></a>
@@ -174,7 +174,7 @@
community at large.</p>
<p>
All Vulnerabilities affecting projects that participate in the
- Simultaneous Release must be reported to the Planning Council prior
+ Simultaneous Release must be reported to the Eclipse Planning Council prior
to full disclosure to the community at large. Disclosure of a
Vulnerability must be coordinated with the distribution of the
updated software from the Project's own distribution channels, the
@@ -200,6 +200,6 @@
<?php
$html = ob_get_contents();
ob_end_clean();
-
+
$App->generatePage($theme, $Menu, $Nav, $pageAuthor, $pageKeywords, $pageTitle, $html);
?>
\ No newline at end of file
