feat(docs): Hugo

[csit.git] / docs / report / introduction / methodology_rca / methodology_perpatch_performance_tests.rst

diff --git a/docs/report/introduction/methodology_rca/methodology_perpatch_performance_tests.rst b/docs/report/introduction/methodology_rca/methodology_perpatch_performance_tests.rst
index 57c5483..9b03c45 100644 (file)
--- a/docs/report/introduction/methodology_rca/methodology_perpatch_performance_tests.rst
+++ b/docs/report/introduction/methodology_rca/methodology_perpatch_performance_tests.rst
@@ -80,9 +80,7 @@ See below for more concrete examples.
 Suite tags
 ``````````
 
-Traditionally, CSIT maintains broad Robot tags that can be used to select tests,
-for details on existing tags, see
-`CSIT Tags <https://github.com/FDio/csit/blob/master/docs/tag_documentation.rst>`_.
+Traditionally, CSIT maintains broad Robot tags that can be used to select tests.
 
 But it is not recommended to use them for test selection,
 as it is not that easy to determine how many test cases are selected.
@@ -124,10 +122,8 @@ and more for dot1q and other encapsulated traffic;
 As there are more test cases than CSIT can periodically test,
 it is possible to encounter an old test case that currently fails.
 To avoid that, you can look at "job spec" files we use for periodic testing,
-for example `this one <https://github.com/FDio/csit/blob/master/docs/job_specs/report_iterative/2n-icx/vpp-mrr-00.md>`_.
+for example `this one <https://github.com/FDio/csit/blob/master/resources/job_specs/report_iterative/2n-icx/vpp-mrr-00.md>`_.
 
-..
-    TODO: Explain why "periodic" job spec link lands at report_iterative.
 
 Shortening triggers
 ```````````````````