Fix broken links

src/blog/how-to-configure-spruce-css-in-your-project.md

@@ -24,10 +24,6 @@ Create a **config** folder inside your **scss** folder. We need an **_index.scss
     └── main.scss
 ```
 
-{% notification %}
-You can see this file structure in action at our [Spruce CSS Starter Kit](https://github.com/conedevelopment/sprucecss-starter-kit).
-{% endnotification %}
-
 ## _index.scss
 
 In this file, we just forward all of the config files.

src/blog/the-simplest-sass-compile-setup.md

@@ -111,7 +111,3 @@ npm run sass-dev
 ```command
 npm run sass-prod
 ```
-
-{% notification %}
-Visit the [Spruce CSS Starter Kit](https://github.com/conedevelopment/sprucecss-starter-kit) to see all of this work.
-{% endnotification %}

src/docs/getting-started/installation.md

@@ -83,5 +83,3 @@ You can control the flow of the style generation in a lot of ways (for more info
 ## Compiling Sass
 
 Depending on your development setup, using Sass could be a burden. We think that Sass is a handy tool and easy to use. Compiling is one of the more significant barriers; for this reason, we wrote an article about [a simple Sass compile setup](https://pineco.de/the-simplest-sass-compile-setup/).
-
-Also, we made a [Spruce CSS Eleventy Starter](https://github.com/conedevelopment/sprucecss-eleventy-starter), a boilerplate starter template based on the popular static site generator 11ty. It includes a basic compile setup and, of course, Spruce CSS. You can find more information about it on GitHub.