-- As part of the LFN cross community guidelines the ONAP documentation project has impelmented the same theme of the docs.onap.org as the the
- other projects within LFN. To have one common way of working with documentation as well as publishing has been a key task during the last years.
-
-- Improvning the structure of docs.onap.org to enhace the user experiance.
-
-- Moving content from the wiki to RTD (read the docs) for better visibility and experiance. Work started and will continue throughout upcoming
- releases.
-
-All JIRA tickets for the Dublin release can be found `ONAP Documentation Jira`_
-
-.. _`ONAP Documentation Jira`: https://jira.onap.org/browse/DOC-476?jql=project%20%3D%20DOC%20AND%20fixVersion%20%3D%20%22Dublin%20Release%22https://docs.opnfv.org
+- Improved end to end user guides.
+- A refined release note template to be used by all projects in ONAP. To ensure
+ a common way of how to provide the release notes from a content such a look
+ and feel perspective.
+- In addition the documentation project is continuously working with improving
+ processes and tools for documentation. Enabling the community to as easy as
+ possible document all the aspects of the ONAP platform. During the Frankfurt
+ release cycle we have started the work to clean up available content, both on
+ the wiki and readthedocs (docs.onap.org) as well as moving the
+ documentation away from submodules according to the LFN documentation
+ strategy.
+
+All JIRA tickets for the Frankfurt release can be found
+`ONAP Documentation Jira`_
+
+.. _`ONAP Documentation Jira`: https://jira.onap.org/browse/DOC-617?jql=project%20%3D%20DOC%20AND%20fixVersion%20%3D%20%22Frankfurt%20Release%22%20