Announce naming standard
diff --git a/generated/news/2019-04-23.html b/generated/news/2019-04-23.html
index 50f8197..56ad562 100644
--- a/generated/news/2019-04-23.html
+++ b/generated/news/2019-04-23.html
@@ -5,7 +5,7 @@
 <!--[if IE]><meta http-equiv="X-UA-Compatible" content="IE=edge"><![endif]-->
 <meta name="viewport" content="width=device-width, initial-scale=1.0">
 <meta name="generator" content="Asciidoctor 1.5.6.1">
-<title>Updated PMC statement for on work Jakarta EE Specifications</title>
+<title>Naming Standard for Jakarta EE Specification Projects</title>
 <style>
 
 </style>
@@ -13,19 +13,37 @@
 </head>
 <body class="article">
 <div id="header">
-<h1>Updated PMC statement for on work Jakarta EE Specifications</h1>
+<h1>Naming Standard for Jakarta EE Specification Projects</h1>
 </div>
 <div id="content">
 <div class="paragraph">
-<p>Date: 2019-04-02</p>
+<p>Date: 2019-04-23</p>
 </div>
 <div class="paragraph">
-<p>Projects may go on with developing new features as well as long as we are able to release Jakarta EE 8 and Eclipse GlassFish 5.2 versions with only the necessary changes required for the release (e.g. name and version number).
-These changes must be possible to merge into the master branch after the release.
-It is up to the projects if they want to keep the ´EE4J_8´ branch for this purpose or create a new release branch from the tag created for the GlassFish 5.1 release.</p>
+<p>The Jakarta EE Specification committee has approved the following naming standard for Jakarta EE Specification projects:</p>
+</div>
+<div class="ulist">
+<ul>
+<li>
+<p>Replace “Java” with “Jakarta” (e.g. “Java Message Service” becomes “Jakarta Message Service”)</p>
+</li>
+<li>
+<p>Add a space in cases where names are mashed together (e.g. “JavaMail” becomes “Jakarta Mail”)</p>
+</li>
+<li>
+<p>Add “Jakarta” when it is missing (e.g. “Expression Language” becomes “Jakarta Expression Language”)</p>
+</li>
+<li>
+<p>Rework names to consistently start with “Jakarta” (“Enterprise JavaBeans” becomes “Jakarta Enterprise Beans”)</p>
+</li>
+<li>
+<p>Simplify/shorten names by removing words that do not add value (e.g. "Jakarta Message Service" becomes "Jakarta Messaging" and "Jakarta Servlet API" becomes "Jakarta Servlet")</p>
+</li>
+</ul>
 </div>
 <div class="paragraph">
-<p>Nightly builds of SNAPSHOT releases for the API projects may be set up for the projects and be made available on build servers, but may not be published through channels such as Maven Central, OSSRH or similar until the trademark agreement between Oracle and Eclipse Foundation regarding the javax.* namespace is finalized.</p>
+<p>The EE4J PMC has been asked to rename the existing specifications according to this standard.
+Tracking of the renaming is shown on the EE4J GitHub organization, <a href="https://github.com/orgs/eclipse-ee4j/projects/11" class="bare">https://github.com/orgs/eclipse-ee4j/projects/11</a></p>
 </div>
 </div>
 </body>