docs: better docs, mv doxygen to sphinx

[vpp.git] / docs / developer / tests / overview.rst

diff --git a/test/doc/overview.rst b/docs/developer/tests/overview.rst
similarity index 98%
rename from test/doc/overview.rst
rename to docs/developer/tests/overview.rst
index 0c07cb6..cc9836e 100644 (file)
--- a/test/doc/overview.rst
+++ b/docs/developer/tests/overview.rst
@@ -118,7 +118,7 @@ The test temporary directory holds the following interesting files:
   named after the interface, so for e.g. pg1, the file will be named
   pg1_out.pcap
 * history files - whenever the capture is restarted or a new stream is added,
-  the existing files are rotated and renamed, soo all the pcap files
+  the existing files are rotated and renamed, so all the pcap files
   are always saved for later debugging if needed
 * core - if vpp dumps a core, it'll be stored in the temporary directory
 * vpp_stdout.txt - file containing output which vpp printed to stdout
@@ -216,7 +216,7 @@ The following APIs are available to the test case for reading pcap files.
   written by the VPP. If using packet infos for verifying packets,
   then the counts of the packet infos can be automatically used by
   `VppPGInterface.get_capture` to get the proper count (in this case
-  the default value None can be supplied as expected_count or ommitted
+  the default value None can be supplied as expected_count or omitted
   altogether).
 * `VppPGInterface.wait_for_packet`: this API is suitable for
   interactive style of test, e.g. when doing session management,
@@ -239,8 +239,8 @@ Automatic filtering of packets:
 Both APIs (`VppPGInterface.get_capture` and
 `VppPGInterface.wait_for_packet`) by default filter the packet
 capture, removing known uninteresting packets from it - these are IPv6
-Router Advertisments and IPv6 Router Alerts. These packets are
-unsolicitated and from the point of |vtf| are random. If a test wants
+Router Advertisements and IPv6 Router Alerts. These packets are
+unsolicited and from the point of |vtf| are random. If a test wants
 to receive these packets, it should specify either None or a custom
 filtering function as the value to the 'filter_out_fn' argument.