[doc] Fix typos

Signed-off-by: Philipp Wagner <phw@lowrisc.org>
diff --git a/doc/ug/getting_started_design.md b/doc/ug/getting_started_design.md
index 43423e4..b8e8c46 100644
--- a/doc/ug/getting_started_design.md
+++ b/doc/ug/getting_started_design.md
@@ -86,7 +86,7 @@
 
 * Get an agreement on if and how the IP block should be integrated.
 * Ensure that the IP block is of acceptable quality.
-* Ensure that the top level simultion is not adversely affected.
+* Ensure that the top level simulation is not adversely affected.
 * Open a Pull Request with the necessary code changes.
 
 If it is not clear on how to proceed, feel free to file an issue requesting assistance.
diff --git a/hw/formal/README.md b/hw/formal/README.md
index 62509b0..161f440 100644
--- a/hw/formal/README.md
+++ b/hw/formal/README.md
@@ -225,7 +225,7 @@
   end
 ```
 
-In constrast, symbolic variable can abstract the design by declaring the index with
+In contrast, symbolic variable can abstract the design by declaring the index with
 constraints. To ensure the symbolic variable performs the expected behaviors,
 two assumptions need to be written:
 * Constraint the symoblic variable with the correct bound
diff --git a/util/testplanner/README.md b/util/testplanner/README.md
index 0e5c713..6d76d00 100644
--- a/util/testplanner/README.md
+++ b/util/testplanner/README.md
@@ -50,7 +50,7 @@
     possible that the planned test needs to be split into multiple smaller tests.
     To cater to these needs, we provide the ability to set a list of actual written
     tests that maps to each planned test. This information will then be used to map
-    the regression results and annotate them to the tesplan to generate the final
+    the regression results and annotate them to the testplan to generate the final
     table. This list does not have to be populated right away. It can be updated
     as and when tests are written.
 
@@ -107,7 +107,7 @@
 enough that they apply to more than one DUTs? We currently solve this by
 providing wildcards, which are single `lower_snake_case` strings within
 braces `'{..}'`. A substitution value (or list of values) for the wildcard
-string can be optionally provided in the DUT tesplan.  Here's an example:
+string can be optionally provided in the DUT testplan.  Here's an example:
 
 ```hjson
 -------
@@ -165,13 +165,13 @@
 The following examples provided within `util/testplanner/examples` can be used as
 a starting point.
 * **`foo_testplan.hjson`**: DUT testplan
-* **`common_testplan.hjson`**: shared testplan imported within the DUT tesplan
-* **`foo_dv_plan.md`**: DUT testplan imported within the DV plan doc in markdown
+* **`common_testplan.hjson`**: shared testplan imported within the DUT testplan
+* **`foo_dv_plan.md`**: DUT testplan imported within the DV plan doc in Markdown
 
 In addition, see the [UART DV Plan]({{< relref "hw/ip/uart/doc/dv_plan" >}}) for a
 real 'production' example of inline expansion of an imported testplan as a table
 within the DV Plan document.
-The [UART tesplan](https://github.com/lowRISC/opentitan/blob/master/hw/ip/uart/data/uart_testplan.hjson)
+The [UART testplan](https://github.com/lowRISC/opentitan/blob/master/hw/ip/uart/data/uart_testplan.hjson)
 imports the shared testplans located at `hw/dv/tools/testplans` area.
 
 ### Limitations
@@ -223,7 +223,7 @@
 ```python
 from testplanner import class_defs, testplan_utils
 
-  # hjson_testplan_path: a string pointing to the path to Hjson tesplan
+  # hjson_testplan_path: a string pointing to the path to Hjson testplan
   # outbuf: file buffer opened for writing
   testplan = testplan_utils.parse_testplan(hjson_testplan_path)
   testplan_utils.gen_html_testplan_table(testplan, outbuf)
diff --git a/util/testplanner/examples/foo_testplan.hjson b/util/testplanner/examples/foo_testplan.hjson
index 2bdca9a..ea2ff2d 100644
--- a/util/testplanner/examples/foo_testplan.hjson
+++ b/util/testplanner/examples/foo_testplan.hjson
@@ -46,7 +46,7 @@
               - A sub-bullet item<br>
                 Continue describing above bullet on a new line with a HTML line break.
 
-            Start a new para with with 2 newlines.
+            Start a new paragraph with with two newlines.
             '''
       milestone: V2
       // testplan entry with multiple tests added