docs: fix GitHub and GitLab brand capitalization

content/blogposts/2021/dev-tool-time-adam-gordon-bell.md

@@ -45,7 +45,7 @@ Missing from Adam’s current setup is the custom-built and programmed split key
 
 > “When I started doing writing ... I want this kind of experience I was used to as a developer, where you have linting, compilers, and a build pipeline that tells you whether things work or not.”
 
-Adam’s main writing environment isn’t Google Docs, or even a speciality Markdown app. It’s [VS Code](https://code.visualstudio.com/), configured with a few plugins and with easy access to a terminal to use command line utilities. Two tools are at the core of his workflow for writing Markdown, the markup language he regularly uses. [`markdownlint`](https://github.com/DavidAnson/markdownlint) analyzes Markdown files according to configurable rules to ensure consistent and well-formed Markdown. It also can automatically fix some common errors. [Vale](https://github.com/errata-ai/vale) provides grammar checking according to custom rules. While Adam uses some of his own rules, the Vale community, which includes companies like Gitlab and Linode, sources a large number of rules, including those to detect “corporate speak!”
+Adam’s main writing environment isn’t Google Docs, or even a speciality Markdown app. It’s [VS Code](https://code.visualstudio.com/), configured with a few plugins and with easy access to a terminal to use command line utilities. Two tools are at the core of his workflow for writing Markdown, the markup language he regularly uses. [`markdownlint`](https://github.com/DavidAnson/markdownlint) analyzes Markdown files according to configurable rules to ensure consistent and well-formed Markdown. It also can automatically fix some common errors. [Vale](https://github.com/errata-ai/vale) provides grammar checking according to custom rules. While Adam uses some of his own rules, the Vale community, which includes companies like GitLab and Linode, sources a large number of rules, including those to detect “corporate speak!”
 
 <Video 
   source={{webm: 'blog/dev-tool-time/adam-gordon-bell/corporate-speak', mp4: 'blog/dev-tool-time/adam-gordon-bell/corporate-speak'}} 

content/blogposts/2023/cody-vscode-0-12-release.md

@@ -62,7 +62,7 @@ In cases where autocompletions don't automatically trigger, you can now request
 
 ### New sign in experience
 
-For new users, you can now sign in to Cody directly using a Github, Gitlab or Google account:
+For new users, you can now sign in to Cody directly using a GitHub, GitLab or Google account:
 
 <img alt="Screenshot of the new sign in page" src="https://storage.googleapis.com/sourcegraph-assets/blog/cody-vscode-0-12-release/sign-in.png" style={{marginTop:"1rem",marginBottom:"1.5rem",marginLeft:0,maxWidth:246}} />
 

content/blogposts/2024/gp-speeding-up-nodejs-development-with-cody.md

@@ -310,7 +310,7 @@ On the left side of VS Code in the Cody tab, you’ll see a  "Generate Unit Test
   src="https://storage.cloud.google.com/sourcegraph-assets/blog/speeding-up-your-node-development-w-cody/image4.png"
 />
 
-With the initial test cases created,I can still edit and add additional test cases according to my needs. Cody makes it easier for me to kickstart my unit testing. The end-to-end testing of the app can be done using any API Client of your choice and the complete code of this app can be found on [Github](https://github.com/oluwatobiisaiah/multimedia-app)
+With the initial test cases created,I can still edit and add additional test cases according to my needs. Cody makes it easier for me to kickstart my unit testing. The end-to-end testing of the app can be done using any API Client of your choice and the complete code of this app can be found on [GitHub](https://github.com/oluwatobiisaiah/multimedia-app)
 
 ## Other use cases Cody in speeding up your Node.js development
 

content/podcast/2.10.md

@@ -601,7 +601,7 @@ I think the people that work on it, not sure if they’re from the original team
 
 And I think that the Code Search for open source, the original one which was launched maybe in 2009 or something became the internal Code Search. And it turned out that at some point the internal Code Search was more popular than the external one.
 
-Nowadays everyone puts their source code, almost everyone, puts their source code on GitHub and then there's this tiny sliver of people that put it on Gitlab, and then there's these corporate weirdos like us that host our own infrastructures.
+Nowadays everyone puts their source code, almost everyone, puts their source code on GitHub and then there's this tiny sliver of people that put it on GitLab, and then there's these corporate weirdos like us that host our own infrastructures.
 
 But just having all the source code on GitHub gives you a central place to get all the source code to index and you get signals about, people put stars on it so you know what is popular and if you know what is popular you can surface more relevant search results. And I think the first version of code search was grabbing random tarballs off the internet, so you've got a lot of duplicate results. And so I think that was a limitation that hampered its functionality and that made it not be very popular.