Update GitLab's contact (#2247)

Author: tancnle

Contributing.md

@@ -10,6 +10,6 @@
 
 4. Please ensure your lexer is for a language that is not primarily used for **blockchain applications**. [Rouge core does not support these](https://github.com/rouge-ruby/rouge/discussions/1857). Again, you are more than welcome to [publish your own plug-in][plugin-example].
 
-5. If your language is too obscure, is internal, not publicly documented, or taking too long for us to get to, **I encourage you to [write your own plugin][plugin-example]**, which you can use easily with Jekyll, Middleman, or self-hosted GitLab. I am not associated with Gitlab - for that, please contact @tancle. For *truly* internal languages, consider just writing a lexer in your own code! This is the approach I took for my own thesis, for example, to nicely highlight in TeX a description of a language that did not yet exist.
+5. If your language is too obscure, is internal, not publicly documented, or taking too long for us to get to, **I encourage you to [write your own plugin][plugin-example]**, which you can use easily with Jekyll, Middleman, or self-hosted GitLab. I am not associated with GitLab - for that, please contact @tancnle. For *truly* internal languages, consider just writing a lexer in your own code! This is the approach I took for my own thesis, for example, to nicely highlight in TeX a description of a language that did not yet exist.
 
 6. Please do not copy/paste other lexers and lightly edit them. If your language is a templating language, please use `TemplateLexer` to support the `?parent=...` argument. If your language embeds another language or is a superset of another language, please subclass the lexer or use delegation as appropriate.