fix: misc typos

Author: f-allian

docs/source/dev/actions_and_webhooks.rst

@@ -4,7 +4,7 @@ Github Actions and Webhooks
 Actions
 --------------
 
-Currently, this project makes use of 4 `Github Actions <https://github.com/features/actions>`_,
+Currently, this project makes use of 5 `Github Actions <https://github.com/features/actions>`_,
 which can be found in the
 `.github/workflows <https://github.com/CITCOM-project/CausalTestingFramework/tree/main/.github/workflows>`_ directory.
 

docs/source/frontends/json_front_end.rst

@@ -60,7 +60,7 @@ The second method of specifying a test is to specify the test in a concrete form
 
 Alternatively, a ``causal_tests.json`` file can be created from a ``dag.dot`` file using the ``causal_testing/specification/metamorphic_relation.py`` script as follows::
 
-  python causal_testing/specification/metamorphic_relation.py --dag_path dag.dot --output_path causal_tests.json
+  python causal_testing/testing/metamorphic_relation.py --dag_path dag.dot --output_path causal_tests.json
 
 Run Commands
 ************
@@ -88,4 +88,4 @@ Runtime Data
 There are currently 2 methods to inputting your runtime data into the JSON frontend:
 
 #. Providing one or more file paths to `.csv` files containing your data
-#. Setting a dataframe to the .data attribute of the JSONUtility instance, this must be done before the setup method is called.
+#. Setting a dataframe to the `.data` attribute of the JSONUtility instance, this must be done before the setup method is called.

docs/source/frontends/test_suite.rst

@@ -7,9 +7,7 @@ This structure is defined by the parameters in the class: :class:`causal_testing
 A current limitation of the Test Suite is that it requires references to the estimator class, not instances (objects) of
 estimator classes, which prevents the usage of some of the features of an estimator.
 
-Class
---------------------
-The test_suite class is an extension of the python UserDict_, meaning it simulates a standard Python dictionary where
+The test_suite class is an extension of the Python UserDict_, meaning it simulates a standard Python dictionary where
 any dictionary method can be used. The class also features a setter to make adding new test cases quicker and less
 error prone :meth:`causal_testing.testing.causal_test_suite.CausalTestSuite.add_test_object`.
 
@@ -23,14 +21,9 @@ the value is a test object in the format of another dictionary:
 Each ``base_test_case`` contains the treatment and outcome variables, and only causal_test_cases testing this relationship
 should be placed in the test object for that ``base_test_case``.
 
-.. _UserDict: https://docs.python.org/3/library/collections.html#collections.UserDict
 
-Execution
------------------------
-The test_suite can be executed by a call to the :meth:`causal_testing.testing.causal_test_engine.CausalTestEngine.execute_test_suite`.
-Here the causal_test_engine will iterate over all the test objects and execute each `test` once per `estimator` and per
-`estimate_type`.
+Following this, users can similarly execute a suite of causal tests and return the results in a list by executing the
+class's :meth:`causal_testing.testing.causal_test_suite.CausalTestSuite.execute_test_suite` method.
+
 
-This structure allows for some optimisations in running cost by only performing certain actions like identification
-when necessary and not for every `causal_test_case`.