Syntax: ST4 specific update for Groovy support

syntaxes/Code Block Syntaxes.sublime-completions

@@ -240,6 +240,14 @@
 			"details": "Specifies <code>GraphViz</code> code highlighting"
 		},
 
+		// Groovy
+		{
+			"trigger": "groovy",
+			"annotation": "Groovy",
+			"kind": ["markup", "s", "Syntax"],
+			"details": "Specifies <code>Groovy</code> code highlighting"
+		},
+
 		// Haskell
 		{
 			"trigger": "haskell",

syntaxes/Markdown.sublime-syntax

@@ -1439,7 +1439,9 @@ contexts:
         6: comment.line.infostring.markdown
         7: meta.fold.code-fence.begin.markdown
       embed: scope:source.groovy
-      embed_scope: markup.raw.code-fence.groovy.markdown-gfm
+      embed_scope:
+        markup.raw.code-fence.groovy.markdown-gfm
+        source.groovy
       escape: '{{fenced_code_block_escape}}'
       escape_captures:
         0: meta.code-fence.definition.end.groovy.markdown-gfm
@@ -3993,7 +3995,7 @@ contexts:
     - meta_scope: meta.link.inet.markdown markup.underline.link.markdown-gfm
     # 1. When an autolink ends in ), we scan the entire autolink for the total
     #    number of parentheses. If there is a greater number of closing parentheses
-    #    than opening ones, we don’t consider the last character part of the
+    #    than opening ones, we don’t consider the last character part of the
     #    autolink, in order to facilitate including an autolink inside a parenthesis
     # 2. If an autolink ends in a semicolon (;), we check to see if it appears to
     #    resemble an entity reference; if the preceding text is & followed by one