design/16339-alias-decls.md: fix formatting of syntax productions

Use bold face to highlight syntax changes (rather than "red" for which
there is no support in markup).

For golang/go#16339.

Change-Id: I2556056d1d45d1c32f504643a564dc9c165b7f27
Reviewed-on: https://go-review.googlesource.com/25048
Reviewed-by: Robert Griesemer <gri@golang.org>
diff --git a/design/16339-alias-decls.md b/design/16339-alias-decls.md
index b57f75b..7e1a19e 100644
--- a/design/16339-alias-decls.md
+++ b/design/16339-alias-decls.md
@@ -406,9 +406,7 @@
 The syntax changes necessary to accommodate alias declarations are limited
 and concentrated. There is a new declaration specification called AliasSpec:
 
-```
-AliasSpec = identifier "=>" PackageName "." identifier .
-```
+**AliasSpec = identifier "=>" PackageName "." identifier .**
 
 An AliasSpec binds an identifier, the alias name, to the object (constant,
 type, variable, or function) the alias refers to. The object must be specified
@@ -418,22 +416,18 @@
 
 Alias specifications may be used with any of the existing constant, type,
 variable, or function declarations. The respective syntax productions are
-extended as follows, with the extensions marked in red:
+extended as follows, with the extensions marked in bold:
 
-```
 ConstDecl = "const" ( ConstSpec | "(" { ConstSpec ";" } ")" ) .
-ConstSpec = IdentifierList [ [ Type ] "=" ExprList ] | AliasSpec .
+ConstSpec = IdentifierList [ [ Type ] "=" ExprList ] **| AliasSpec** .
 
 TypeDecl  = "type" ( TypeSpec | "(" { TypeSpec ";" } ")" ) .
-TypeSpec  = identifier Type | AliasSpec .
+TypeSpec  = identifier Type **| AliasSpec** .
 
 VarDecl   = "var" ( VarSpec | "(" { VarSpec ";" } ")" ) .
-VarSpec   = IdentList ( Type [ "=" ExprList ] | "=" ExprList ) |
-            AliasSpec .
+VarSpec   = IdentList ( Type [ "=" ExprList ] | "=" ExprList ) **| AliasSpec** .
 
-FuncDecl  = "func" FunctionName ( Function | Signature ) |
-            "func" AliasSpec .
-```
+FuncDecl  = "func" FunctionName ( Function | Signature ) **| "func" AliasSpec** .
 
 ## A2. Alternatives to this proposal
 For completeness, we mention several alternatives.