From 5e8172aaa70c8f1ffd4c1b58b35d73f27bf4b6af Mon Sep 17 00:00:00 2001
From: JSON <49416440+JSON@users.noreply.github.com>
Date: Thu, 11 Apr 2019 22:09:31 -0500
Subject: [PATCH] Update README.md (#897)

---
 specs/test_formats/README.md | 4 ++--
 1 file changed, 2 insertions(+), 2 deletions(-)

diff --git a/specs/test_formats/README.md b/specs/test_formats/README.md
index 371c489b65..2c1ef2d038 100644
--- a/specs/test_formats/README.md
+++ b/specs/test_formats/README.md
@@ -7,7 +7,7 @@ This document defines the YAML format and structure used for ETH 2.0 testing.
 * [About](#about)
 * [Glossary](#glossary)
 * [Test format philosophy](#test-format-philosophy)
-* [Test Suite](#yaml-suite)
+* [Test Suite](#test-suite)
 * [Config](#config)
 * [Fork-timeline](#fork-timeline)
 * [Config sourcing](#config-sourcing)
@@ -28,7 +28,7 @@ The particular formats of specific types of tests (test suites) are defined in s
 - `suite`: a YAML file with:
   - a header: describes the `suite`, and defines what the `suite` is for
   - a list of test cases
-- `runner`: where a generator is a *"producer"*, this is the *"consumer"**.
+- `runner`: where a generator is a *"producer"*, this is the *"consumer"*.
   - A `runner` focuses on *only one* `type`, and each type has *only one* `runner`.
 - `handler`: a `runner` may be too limited sometimes, you may have a `suite` with a specific focus that requires a different format.
   To facilitate this, you specify a `handler`: the runner can deal with the format by using the specified handler.