make all links great again

Navigation/Spaghetti/Unsequence.tax

@@ -9,7 +9,7 @@ experience optimal.
 
 In the past we have been using a grammar mutation called
 [emph]SubGrammar[/emph] to improve the readability of grammars extracted from
-language manuals [cite]SLEIR2014[/cite]. It would reorder the rules in the
+language manuals [gwnet]SLEIR2014[/gwnet]. It would reorder the rules in the
 following way: grab the starting symbol (usually the root of the grammar) and
 list all its production rules, and then go through all nonterminals used in
 their right hand sides one by one in the same sequence that they occur, add

Organisation/Convention/Misnomer.tax

@@ -17,7 +17,7 @@ also investigate whether naming [emph]policies[/emph] are present and how they
 are respected. For instance, if all nonterminals are camelcased, but one is
 lowercase with an underscore separator, it was probably a misspelling---cases
 like this were reported in a MediaWiki grammar which was created by several
-unrelated grammar engineers [cite]MediaWiki2011[/cite]. If can also be the
+unrelated grammar engineers [gwnet]MediaWiki2011[/gwnet]. If can also be the
 case that the naming policy carries semantic meaning: typically lexical
 nonterminals and/or preterminals are named in uppercase, to distinguish them
 visually when they are used next to others like this:

Organisation/Duplication/Echo.tax

@@ -7,4 +7,5 @@ both the grammar and language documentation. They were merged in the grammar
 extractor---that is, during the phase of converting the original HTML document
 to the first version of the grammar [cite]p.348/SCAM-J-2009-LammelZ11[/cite].
 A similar error was observed earlier in the C\# standard
-[cite]Too-Sharp2005[/cite] and later in other languages [cite]Zoo2015[/cite].
+[gwnet]Too-Sharp2005[/gwnet] and later in other languages
+[gwnet]Zoo2015[/gwnet].

Organisation/Parsing/Shotgun.tax

@@ -7,13 +7,13 @@ architecture where a proper parser is substituted with lightweight treatment
 tools built with such defects, the problems quickly multiply with each step
 when the receiver is applying Postel's Law in trying to be relaxed with its
 input [cite]Sassaman2012[/cite], and is known to cause all kinds of subtle
-bugs in software language processing [cite]Flexible2015[/cite]. We define the
-Shotgun smell as a situation when the grammatical bind is too loose on one of
-its ends. For example, imagine function arguments in a C-like language to be
-parsed as a parenthesis-enclosing string which is expected to be split into a
-proper list by the code that uses the resulting tree. This smell was not seen
-within grammars of the Grammar Zoo, but was observed in the industrial setting
-when time pressure got the best of grammar engineers.
+bugs in software language processing [gwnet]Flexible2015[/gwnet]. We define
+the Shotgun smell as a situation when the grammatical bind is too loose on one
+of its ends. For example, imagine function arguments in a C-like language to
+be parsed as a parenthesis-enclosing string which is expected to be split into
+a proper list by the code that uses the resulting tree. This smell was not
+seen within grammars of the Grammar Zoo, but was observed in the industrial
+setting when time pressure got the best of grammar engineers.
 
 Related: MA|Missing Abstraction
 Related: MAC2|Missing Abstraction

Structure/Dependency/Diamond.tax

@@ -17,6 +17,6 @@ delegate-type ::= type-name ;
 Parsing something recognisable as [code]type-name[/code] will cause at least a
 triple ambiguity since it will be an acceptable [code]class-type[/code],
 [code]interface-type[/code] as well as [code]delegate-type[/code]
-[cite]Too-Sharp2005[/cite].
+[gwnet]Too-Sharp2005[/gwnet].
 
 Related: AAI|Ambiguous Interfaces