diff --git a/xavishobbies/content/web_development/building_with_hugo.md b/xavishobbies/content/web_development/building_with_hugo.md
index b68441c..98bbd4e 100644
--- a/xavishobbies/content/web_development/building_with_hugo.md
+++ b/xavishobbies/content/web_development/building_with_hugo.md
@@ -10,7 +10,7 @@ As much as I started to enjoy playing around and styling with *html/css*, it did
 
 What I was looking for was an environment that was *extensible* enough to eliminate redundant code while also *malleable* enough to execute the initial vision I had for the website **[i know, surprising this website had any vision at all given the look]**. Static site generators enable this by, essentially, copying identical html across multiple pages through *templates*. This maintains the benefits of a static site while addressing one of it's biggest drawbacks. After some research **[googling "best static site generator"]**,  [Hugo](https://gohugo.io/) seemed to check the boxes I had in mind and also looked relatively simple to implement **[which is something a lazy person like me really values]**.
 
-After installing on a local machine with `apt install hugo` **[change apt to your respective package manager]**, a new site can be created in *Hugo* with the command `hugo new site site_name` which creates a directory with Hugo's default file structure. The main directories that I use are *content*, *layouts*, and *static*. *Content* is where the actual content of a *post* is stored **[basically the actual content of the website]**,  *layouts* is where *templates* and other *code snippets* are defined **[where hugo pulls the skeleton html to generate posts and lists]**, and *static* is where things that are referenced by templates and posts are stored **[like images and style sheets]**.
+After installing on a local machine with `apt install hugo` **[change apt to your respective package manager]**, a new site can be created with *Hugo* with the command `hugo new site site_name` which creates a directory with Hugo's default file structure. The main directories that I use are *content*, *layouts*, and *static*. *Content* is where the actual content of a *post* is stored **[basically the actual meat of the website]**,  *layouts* is where *templates* and other *code snippets* are defined **[where hugo pulls the skeleton html to generate posts and lists]**, and *static* is where things that are referenced by templates and posts are stored **[like images and style sheets]**.
 
 New content posts can be created with `hugo new section_name/post.md` which creates a new file under *content/section_name/post.md*. For example this post was created with `hugo new web_development /building_with_hugo.md`. Section landing pages can be created by adding a *_index.md* file under the section directory with `hugo new section_name/_index.md` **[these will call the *list* template, if you don't know what that means, *read on!*]**.