Changing CVP to OVP in the documentation

Due to the name change from 'CVP' to 'OVP', the documentation has to be
updated.

Change-Id: Id934e8fc07f60802f7aa6b3d295d268c4c9b71f8
Signed-off-by: Georg Kunz <georg.kunz@ericsson.com>

1 files changed, 13 insertions, 13 deletions

diff --git a/docs/testing/user/systempreparation/index.rst b/docs/testing/user/systempreparation/index.rst
index fe1f60d6..afc5dc47 100644
--- a/docs/testing/user/systempreparation/index.rst
+++ b/docs/testing/user/systempreparation/index.rst
@@ -5,25 +5,25 @@
 
 .. _dovetail-system_preparation_guide:
 
-============================================================
-Compliance Verification Program system preparation guide
-============================================================
+===============================================
+OPNFV Verified Program system preparation guide
+===============================================
 
 This document provides a general guide to hardware system prerequisites
-and expectations for running OPNFV CVP testing. For detailed guide of
+and expectations for running OPNFV OVP testing. For detailed guide of
 preparing software tools and configurations, and conducting the test,
 please refer to the User Guide :ref:dovetail-testing_user_guide.
 
-The CVP test tools expect that the hardware of the System Under Test (SUT)
+The OVP test tools expect that the hardware of the System Under Test (SUT)
 is Pharos compliant `Pharos specification`_
 
 The Pharos specification itself is a general guideline, rather than a set of
 specific hard requirements at this time, developed by the OPNFV community. For
-the purpose of helping CVP testers, we summarize the main aspects of hardware to
-consider in preparation for CVP testing.
+the purpose of helping OVP testers, we summarize the main aspects of hardware to
+consider in preparation for OVP testing.
 
-As described by the CVP Testing User Guide, the hardware systems involved in
-CVP testing includes a Test Node, a System Under Test (SUT) system, and network
+As described by the OVP Testing User Guide, the hardware systems involved in
+OVP testing includes a Test Node, a System Under Test (SUT) system, and network
 connectivity between them.
 
 The Test Node can be a bare metal machine or a virtual machine that can support
@@ -39,13 +39,13 @@ ARM-64. Mixing different architectures in the same SUT is not supported.
 
 A minimum of 5 servers, 3 configured for controllers and 2 or more configured for compute
 resource are expected. However this is not a hard requirement
-at this phase. The CVP 1.0 mandatory test cases only require one compute server. At
+at this phase. The OVP 1.0 mandatory test cases only require one compute server. At
 lease two compute servers are required to pass some of the optional test cases
-in the current CVP release. CVP control service high availability tests expect two
+in the current OVP release. OVP control service high availability tests expect two
 or more control nodes to pass, depending on the HA mechanism implemented by the
 SUT.
 
-The SUT is also expected to include components for persistent storage. The CVP
+The SUT is also expected to include components for persistent storage. The OVP
 testing does not expect or impose significant storage size or performance requirements.
 
 The SUT is expected to be connected with high performance networks. These networks
@@ -56,7 +56,7 @@ and compute services in the SUT
 - A data network that supports the virtual network capabilities and data path testing
 
 Additional networks, such as Light Out Management or storage networks, may be
-beneficial and found in the SUT, but they are not a requirement for CVP testing.
+beneficial and found in the SUT, but they are not a requirement for OVP testing.
 
 .. References
 .. _`Pharos specification`: https://wiki.opnfv.org/display/pharos/Pharos+Specification