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>
(cherry picked from commit 8f16dae9dae6d13bc6f5934bae5d26d420efd892)

1 files changed, 0 insertions, 71 deletions

diff --git a/docs/testing/user/index.rst b/docs/testing/user/index.rst
deleted file mode 100644
index 120aba45..00000000
--- a/docs/testing/user/index.rst
+++ /dev/null
@@ -1,71 +0,0 @@
-.. This work is licensed under a Creative Commons Attribution 4.0 International License.
-.. http://creativecommons.org/licenses/by/4.0
-.. (c) Ericsson AB
-
-======================================================
-Compliance and Verification program user documentation
-======================================================
-
-.. toctree::
-   :maxdepth: 2
-
-Version history
-===============
-
-+------------+----------+------------------+----------------------------------+
-| **Date**   | **Ver.** | **Author**       | **Comment**                      |
-|            |          |                  |                                  |
-+------------+----------+------------------+----------------------------------+
-| 2017-03-15 | 0.0.1    | Chris Price      | Draft version                    |
-|            |          |                  |                                  |
-+------------+----------+------------------+----------------------------------+
-
-
-Introduction
-============
-
-This document provides all relevant user documentation for executing the OPNFV
-compliance and certification program (CVP).  The CVP provides mechanisms for evaluating
-NFV infrastructures to establish their alignment with the target architectures, behaviours
-and functions defined by the OPNFV community.
-
-Compliance and Verification Program guidelines
-==============================================
-
-The CVP provides publicly available mechanisms for evaluating compliance to OPNFV concepts,
-behaviours and architectures.  The CVP, through the Compliance and Certification
-committee, is responsible for evaluating the results of any evaluations and providing
-access to any associated OPNFV branding.  Details of the CVP are described in the `CVP Document.`_
-
-"Add the final CVP doc URL in plain text here"
-
-Compliance and Verification program test specification
-======================================================
-
-The `test specification`_ provides an outline of the prerequisites, methods, tools
-& areas that are applicable to the CVP test process.  The `test specification`_ is intended
-to give a use a comprehensive overview of what is expected of engineer prior to running
-the NFV platform evaluation suite, what tools and processes will be used during the
-evaluation and a guide as to how the results of the tests will be interpreted.  It is advised
-that all practitioners of the CVP read the `test specification`_ prior to beginning
-the process of evaluation.
-
-"Add the final test spec URL in plain text here"
-
-Compliance and Verification program Test Plan
-=============================================
-
-The test spec will outline the processes & areas and the test case descriptions included.
-This document will in addition outline how to modularise the areas to be executed, how to
-run each area and when the testing process begins and ends.
-
-Compliance and Verification program Test results
-================================================
-
-To be added once our test result reporting system and processes are defined.
-
-References
-==========
-
-.. _`CVP Document.`: https://opnfv.org
-.. _`test specification`: https://opnfv.org