summaryrefslogtreecommitdiffstats
diff options
context:
space:
mode:
authorrpaik <rpaik@linuxfoundation.org>2017-10-06 09:56:28 -0700
committerrpaik <rpaik@linuxfoundation.org>2017-10-06 09:57:05 -0700
commit9e647944a5b30b1944aa6bfa174aff149cd60d59 (patch)
treeacefc5dddba21774fe11bb3cc2560aeff224c621
parent99855d1099e3a1fed81d18d485b2b50b403da5c2 (diff)
Made minor edits.
Change-Id: Ie38d1938156578ca8ce97cb2ecc177294cb578cc Signed-off-by: rpaik <rpaik@linuxfoundation.org>
-rw-r--r--docs/release/installation.introduction.rst6
-rw-r--r--docs/release/release-notes.rst4
-rw-r--r--docs/release/userguide.introduction.rst14
3 files changed, 12 insertions, 12 deletions
diff --git a/docs/release/installation.introduction.rst b/docs/release/installation.introduction.rst
index c45866684..cdf1479b2 100644
--- a/docs/release/installation.introduction.rst
+++ b/docs/release/installation.introduction.rst
@@ -11,7 +11,7 @@ Installation
Abstract
========
-This document provides an overview of the installation of the Euphrates release of OPNFV.
+This an overview document for the installation of the Euphrates release of OPNFV.
The Euphrates release can be installed making use of any of the installer projects in OPNFV:
Apex, Compass4Nfv, Daisy4NFV, Fuel or JOID. Each installer provides the ability to install a common OPNFV
@@ -105,9 +105,9 @@ The instructions for each toolchain can be found in these links:
OPNFV Test Frameworks
=====================
-If you have elected to install the OPNFV platform using the deployment toolchain provided by OPNFV
+If you have elected to install the OPNFV platform using the deployment toolchain provided by OPNFV,
your system will have been validated once the installation is completed.
-The basic deployment validation only addresses a small part of capabilities provided in
+The basic deployment validation only addresses a small part of capabilities in
the platform and you may want to execute more exhaustive tests. Some investigation will be required to
select the right test suites to run on your platform.
diff --git a/docs/release/release-notes.rst b/docs/release/release-notes.rst
index 8039c53bd..9e6e5c301 100644
--- a/docs/release/release-notes.rst
+++ b/docs/release/release-notes.rst
@@ -7,8 +7,8 @@
Release Notes
=============
-Release notes as provided by the OPNFV participating projects are captured in this section.
-These include details of software versions used, known limitations and outstanding trouble
+Release notes as provided by participating projects in OPNFV are captured in this section.
+These include details of software versions used, known limitations, and outstanding trouble
reports.
Project release notes:
diff --git a/docs/release/userguide.introduction.rst b/docs/release/userguide.introduction.rst
index b7f42521b..ef48e590c 100644
--- a/docs/release/userguide.introduction.rst
+++ b/docs/release/userguide.introduction.rst
@@ -14,11 +14,11 @@ Abstract
OPNFV is a collaborative project aimed at providing a variety of virtualisation
deployments intended to host applications serving the networking and carrier
industries. This document provides guidance and instructions for using platform
-features designed to support these applications, made available in the OPNFV
+features designed to support these applications that are made available in the OPNFV
Euphrates release.
This document is not intended to replace or replicate documentation from other
-upstream open source projects such as KVM, OpenDaylight, or OpenStack, but to highlight the
+upstream open source projects such as KVM, OpenDaylight, OpenStack, etc., but to highlight the
features and capabilities delivered through the OPNFV project.
@@ -28,14 +28,14 @@ Introduction
OPNFV provides a suite of scenarios, infrastructure deployment options, which
are able to be installed to host virtualised network functions (VNFs).
This document intends to help users of the platform leverage the features and
-capabilities delivered by the OPNFV project.
+capabilities delivered by OPNFV.
OPNFVs' Continuous Integration builds, deploys and tests combinations of virtual
infrastructure components in what are defined as scenarios. A scenario may
include components such as KVM, OpenDaylight, OpenStack, OVS, etc., where each
scenario will include different source components or configurations. Scenarios
are designed to enable specific features and capabilities in the platform that
-can be leveraged by the OPNFV User community.
+can be leveraged by the OPNFV user community.
Feature Overview
@@ -44,15 +44,15 @@ Feature Overview
The following links outline the feature deliverables from participating OPNFV
projects in the Euphrates release. Each of the participating projects provides
detailed descriptions about the delivered features including use cases,
-implementation and configuration specifics.
+implementation, and configuration specifics.
The following Configuration Guides and User Guides assume that the reader already has some
-information about a given project's specifics and deliverables. These Guides
+knowledge about a given project's specifics and deliverables. These Guides
are intended to be used following the installation with an OPNFV installer
to allow users to deploy and implement feature delivered by OPNFV.
If you are unsure about the specifics of a given project, please refer to the
-OPNFV wiki page at http://wiki.opnfv.org, for more details.
+OPNFV wiki page at http://wiki.opnfv.org for more details.
Feature Configuration Guides