Small fixes in dynamic parameter docs

delatrie · delatrie · commit 6ec8abf072ed · 2023-01-30T12:19:00.000+03:00
diff --git a/allure-pytest/examples/parameter/dynamic_parameter.rst b/allure-pytest/examples/parameter/dynamic_parameter.rst
@@ -18,7 +18,7 @@ tree view.
 Affecting the history of test execution in Allure TestOps
 ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
 
-Parameters also affect how Allure TestOps keeps test history and retry records
+Parameters also affect how Allure TestOps keeps history and retry records
 across test results. Two test results that differs from each other in a
 parameter value are considered as belonging to different test cases, thus
 forming separate histories.
@@ -43,7 +43,7 @@ Masking a sensitive parameter
 ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
 
 A parameter value can be masked with ``mode`` argument. The masked value is shown
-as `******` in the report. This is useful for sensitive parameters like
+as ``******`` in the report. This is useful for sensitive parameters like
 passwords or key phrases:
 
 
@@ -53,9 +53,9 @@ passwords or key phrases:
     ...     allure.dynamic.parameter("password", "qwerty", mode=allure.parameter_mode.MASKED)
 
 
-.. warning:: Although the value is masked in the report, it is still present in the
-    test result files (but not in report files, i.e., generated by allure
-    reporter).
+WARNING: Although the value is masked in the report, it is still present in the
+    test result files (but not in report files, i.e., the files generated by
+    allure reporter).
 
 
 Hiding a parameter from the report
