Github username update

content/posts/a_modern_terminal_workflow_1.md

@@ -11,7 +11,7 @@ Perhaps you’re a tinkerer, a javascript ninja, or something else entirely it
 
 This is an opinionated walkthrough using tools both new and old that are performant and work well together. Through a combination of Git, NeoVim, Zsh, Tmux and iTerm2 this article will take you step by step in writing a dotfiles repo to set up a MacOS programming environment.
 
-Optionally, skip ahead and [see the final result](https://github.com/sharpshark28/modern-terminal-workflow).
+Optionally, skip ahead and [see the final result](https://github.com/hergaiety/modern-terminal-workflow).
 
 ## What is a Dotfile?
 

content/posts/learning_on_rails.md

@@ -16,5 +16,5 @@ Taking the time to learn Rails has better framed my understanding of the Javascr
 
 I never felt a need to venture outside of my bubble before. But by intentionally doing so, I realized the bubble only harmed by ability to learn rather than protect me in some way. There's no need to be afraid of learning. You never know just how much it may help you.
 
-Finally, I encourage you to document and share what you learn. I've published [my hello world's in both Ruby and Rails](https://github.com/sharpshark28/hello-ruby) and highly recommend [rubyonrail.org's Getting Started guide](https://guides.rubyonrails.org/getting_started.html#hello-rails-bang) if you'd like to get started with Rails and learn something fun.
+Finally, I encourage you to document and share what you learn. I've published [my hello world's in both Ruby and Rails](https://gitlab.com/gaiety/hello-learning/-/tree/ruby-on-rails) and highly recommend [rubyonrail.org's Getting Started guide](https://guides.rubyonrails.org/getting_started.html#hello-rails-bang) if you'd like to get started with Rails and learn something fun.
 

content/posts/the_great_app_store_trials.md

@@ -78,7 +78,7 @@ JSON cannot be fetched locally as we could on Netlify. I did not wish to bake in
 
 For my web app, the only concern with baking in data was app size for first load. On mobile that's not a problem. In fact, baking in the data means an even easier offline solution.
 
-I wrote a [data processor](https://github.com/sharpshark28/my_spells/blob/master/build/process_spells.js) node script that could either compile my data to a JSON file or to a JS importable module (with `export default ...`) along with some [package.json build scripts](https://github.com/sharpshark28/my_spells/blob/master/package.json) to simplify the process during development and releases. In the app, I always import the JS module and if there is `data.length > 0` I use it, else I attempt to fetch the JSON file.
+I wrote a [data processor](https://github.com/hergaiety/my_spells/blob/master/build/process_spells.js) node script that could either compile my data to a JSON file or to a JS importable module (with `export default ...`) along with some [package.json build scripts](https://github.com/hergaiety/my_spells/blob/master/package.json) to simplify the process during development and releases. In the app, I always import the JS module and if there is `data.length > 0` I use it, else I attempt to fetch the JSON file.
 
 It took effort, but assured that my both the web and android app were quick to launch.