BIP 9: Use simple Yes/No rather than templates (which don't work on GitHub)

Author: luke-jr

bip-0009.mediawiki

@@ -170,7 +170,7 @@ The template request Object is extended to include a new item:
 |-
 ! Key !! Required !! Type !! Description
 |-
-| rules || {{No}} || Array of Strings || list of supported softfork deployments, by name
+| rules || No || Array of Strings || list of supported softfork deployments, by name
 |}
 
 The template Object is also extended:
@@ -180,11 +180,11 @@ The template Object is also extended:
 |-
 ! Key !! Required !! Type !! Description
 |-
-| rules || {{Yes}} || Array of Strings || list of softfork deployments, by name, that are active state
+| rules || Yes || Array of Strings || list of softfork deployments, by name, that are active state
 |-
-| vbavailable || {{Yes}} || Object || set of pending, supported softfork deployments; each uses the softfork name as the key, and the softfork bit as its value
+| vbavailable || Yes || Object || set of pending, supported softfork deployments; each uses the softfork name as the key, and the softfork bit as its value
 |-
-| vbrequired || {{No}} || Number || bit mask of softfork deployment version bits the server requires enabled in submissions
+| vbrequired || No || Number || bit mask of softfork deployment version bits the server requires enabled in submissions
 |}
 
 The "version" key of the template is retained, and used to indicate the server's preference of deployments.