Minor fix markdown format

4 files changed, 6 insertions, 7 deletions

diff --git a/contributors/design-proposals/scheduling/nodeaffinity.md b/contributors/design-proposals/scheduling/nodeaffinity.md
index adab5dde..ae167ce5 100644
--- a/contributors/design-proposals/scheduling/nodeaffinity.md
+++ b/contributors/design-proposals/scheduling/nodeaffinity.md
@@ -144,7 +144,7 @@ Hopefully this won't cause too much confusion.
 
 ## Examples
 
-** TODO: fill in this section **
+**TODO: fill in this section**
 
 * Run this pod on a node with an Intel or AMD CPU
 
diff --git a/contributors/design-proposals/scheduling/podaffinity.md b/contributors/design-proposals/scheduling/podaffinity.md
index 01947728..666caaea 100644
--- a/contributors/design-proposals/scheduling/podaffinity.md
+++ b/contributors/design-proposals/scheduling/podaffinity.md
@@ -345,8 +345,7 @@ as shorthand for "RequiredDuringSchedulingScheduling pod affinity" and
 "SoftPodAffinity" as shorthand for "PreferredDuringScheduling pod affinity."
 Analogously for "HardPodAntiAffinity" and "SoftPodAntiAffinity."
 
-** TODO: Update this algorithm to take weight for SoftPod{Affinity,AntiAffinity}
-into account; currently it assumes all terms have weight 1. **
+**TODO: Update this algorithm to take weight for SoftPod{Affinity,AntiAffinity} into account; currently it assumes all terms have weight 1.**
 
 ```
 Z = the pod you are scheduling
@@ -664,5 +663,5 @@ This proposal is to satisfy [#14816](https://github.com/kubernetes/kubernetes/is
 
 ## Related work
 
-** TODO: cite references **
+**TODO: cite references**
 
diff --git a/contributors/design-proposals/storage/raw-block-pv.md b/contributors/design-proposals/storage/raw-block-pv.md
index 17e6b61f..f180845e 100644
--- a/contributors/design-proposals/storage/raw-block-pv.md
+++ b/contributors/design-proposals/storage/raw-block-pv.md
@@ -423,7 +423,7 @@ Spec:
   gcePersistentDisk:
     pdName: "gce-disk-1"
 ```
-***Since the PVC object is passed to the provisioner, it will be responsible for validating and handling whether or not it supports the volumeMode being passed ***
+**Since the PVC object is passed to the provisioner, it will be responsible for validating and handling whether or not it supports the volumeMode being passed**
 
 ## UC8:
 
@@ -557,7 +557,7 @@ spec:
         claimName: block-pvc001
         readOnly: true #flag indicating read-only for container runtime
 ```
-*** Note: the readOnly field already exists in the PersistentVolumeClaimVolumeSource above and will dictate the values set by the container runtime options ***
+**Note: the readOnly field already exists in the PersistentVolumeClaimVolumeSource above and will dictate the values set by the container runtime options**
 
 
 # Container Runtime considerations
diff --git a/contributors/devel/architectural-roadmap.md b/contributors/devel/architectural-roadmap.md
index 8048264d..9d8a6f31 100644
--- a/contributors/devel/architectural-roadmap.md
+++ b/contributors/devel/architectural-roadmap.md
@@ -1126,7 +1126,7 @@ answer:
           feature (by asking the user what cloud provider they have,
           or in the future a feature discovery API).
 
-* **Kubernetes Security Models **
+* **Kubernetes Security Models**
 
     * Audience: hosters, distributors, custom cluster builders