From 499f02a9ee34df8c5c866d52723abd838fce6f22 Mon Sep 17 00:00:00 2001 From: bpcreech <35012922+bpcreech@users.noreply.github.com> Date: Sun, 4 Feb 2024 19:42:07 -0500 Subject: [PATCH] Update how-this-works.md --- content/post/how-this-works.md | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) diff --git a/content/post/how-this-works.md b/content/post/how-this-works.md index 22cbbea..e24f16c 100644 --- a/content/post/how-this-works.md +++ b/content/post/how-this-works.md @@ -33,10 +33,10 @@ by Arnab Kumar Shil shows how to: schlep that generatic content into [_another_ Github repo](https://github.com/bpcreech/bpcreech.github.io). 3. From _there_ the built-in [Github Pages](https://pages.github.com/) Github - Actions automatically update bpcreech.github.io with that content. + Actions automatically update [bpcreech.github.io](https://bpcreech.github.io) with that content. 4. We can also, thanks to Github Pages' [custom domains feature](https://docs.github.com/en/pages/configuring-a-custom-domain-for-your-github-pages-site/about-custom-domains-and-github-pages), - redirect traffic from bpcreech.com to bpcreech.github.io at the DNS layer. + redirect traffic from [bpcreech.com](https://bpcreech.com) to [bpcreech.github.io](https://bpcreech.github.io) at the DNS layer. - One cool part about this which I wasn't expecting: Github pages [automatically obtains](https://docs.github.com/en/pages/getting-started-with-github-pages/securing-your-github-pages-site-with-https)