aboutsummaryrefslogtreecommitdiffstats
path: root/docs
diff options
context:
space:
mode:
authorLasse Kaihlavirta <l.kaihlavirt@partner.samsung.com>2020-11-05 13:59:06 +0200
committerMorgan Richomme <morgan.richomme@orange.com>2020-11-06 07:27:09 +0000
commitee40480d667bb9a5b854254217fef11bbe065644 (patch)
tree9fa296676812d70ed7f3d52481fb3d82c985e1b5 /docs
parente0e213334c3a8f44d0a2a386c413de1ca8e28036 (diff)
Minor corrections to doc index
Issue-ID: INT-1759 Signed-off-by: Lasse Kaihlavirta <l.kaihlavirt@partner.samsung.com> Change-Id: I3031e2fcea13983bc55fba83ee0b274d2049ed46 Signed-off-by: mrichomme <morgan.richomme@orange.com>
Diffstat (limited to 'docs')
-rw-r--r--docs/docs_5G_PNF_Software_Upgrade.rst6
-rw-r--r--docs/index.rst6
2 files changed, 6 insertions, 6 deletions
diff --git a/docs/docs_5G_PNF_Software_Upgrade.rst b/docs/docs_5G_PNF_Software_Upgrade.rst
index 6b8e5d2d6..cec02f9fd 100644
--- a/docs/docs_5G_PNF_Software_Upgrade.rst
+++ b/docs/docs_5G_PNF_Software_Upgrade.rst
@@ -26,15 +26,15 @@ PNF Software Upgrade Scenarios
There are 3 PNF software upgrade scenarios supported in Frankfurt release:
-* `Using direct Netconf/Yang interface with PNF <docs_5G_PNF_Software_Upgrade_direct_netconf_yang.html>`_
+* `Using direct Netconf/Yang interface with PNF <docs_5G_PNF_Software_Upgrade_direct_netconf_yang>`
- (https://wiki.onap.org/pages/viewpage.action?pageId=64007309)
-* `Using Ansible protocol with EM <docs_5G_PNF_Software_Upgrade_ansible_with_EM.html>`_
+* `Using Ansible protocol with EM <docs_5G_PNF_Software_Upgrade_ansible_with_EM>`
- (https://wiki.onap.org/pages/viewpage.action?pageId=64007357)
-* `Using Netconf/Yang interface with EM <docs_5G_PNF_Software_Upgrade_netconf_with_EM.html>`_
+* `Using Netconf/Yang interface with EM <docs_5G_PNF_Software_Upgrade_netconf_with_EM>`
- (https://wiki.onap.org/pages/viewpage.action?pageId=64008675)
diff --git a/docs/index.rst b/docs/index.rst
index c6bbd7109..0096406d6 100644
--- a/docs/index.rst
+++ b/docs/index.rst
@@ -7,7 +7,7 @@ INTEGRATION
The Integration project is in charge of:
- Providing testing environment and support for the release use cases
-- Executing Cross-project Continuous System Integration Testing (CSIT)
+- Executing project-specific Continuous System Integration Testing (CSIT)
- Managing full ONAP CI chains (daily master, staging, stable) to ensure the
stability of the integration
- Developing and performing tests within full ONAP context (healthcheck, End to
@@ -20,8 +20,8 @@ For each release, the integration team provides the following artifacts:
- Use-case documentation and artifacts
- a testsuite docker included in ONAP cluster to execute the tests
- baseline JAVA and Python images, as well as a docker managing Java libraries
-- Configuration fiales and Heat templates to simplify the creation of the virtual
- ressources needed for the ONAP deployment and the use cases.
+- Configuration files and Heat templates to simplify the creation of the virtual
+ resources needed for the ONAP deployment and the use cases.
The integration team manages several official ONAP repositories: