From 259eec5ab5b5f4130af14a5fe45eff6c879426e6 Mon Sep 17 00:00:00 2001
From: kevindelsh <44755032+kevindelsh@users.noreply.github.com>
Date: Mon, 4 Mar 2019 16:35:07 +0100
Subject: [PATCH] Sass import doesn't need file extension (#34802)
Added that the Sass import statement doesn't need the file extension like it doesn't need the underscore.
This helps beginners to better understand the concept and avoid confusion.
---
...lit-your-styles-into-smaller-chunks-with-partials.english.md | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/curriculum/challenges/english/03-front-end-libraries/sass/split-your-styles-into-smaller-chunks-with-partials.english.md b/curriculum/challenges/english/03-front-end-libraries/sass/split-your-styles-into-smaller-chunks-with-partials.english.md
index e77b0011da..a4010ab2ea 100644
--- a/curriculum/challenges/english/03-front-end-libraries/sass/split-your-styles-into-smaller-chunks-with-partials.english.md
+++ b/curriculum/challenges/english/03-front-end-libraries/sass/split-your-styles-into-smaller-chunks-with-partials.english.md
@@ -10,7 +10,7 @@ challengeType: 0
Names for partials start with the underscore (_) character, which tells Sass it is a small segment of CSS and not to convert it into a CSS file. Also, Sass files end with the .scss file extension. To bring the code in the partial into another Sass file, use the @import directive.
For example, if all your mixins are saved in a partial named "_mixins.scss", and they are needed in the "main.scss" file, this is how to use them in the main file:
// In the main.scss file
@import 'mixins'
-Note that the underscore is not needed in the import statement - Sass understands it is a partial. Once a partial is imported into a file, all variables, mixins, and other code are available to use.
+Note that the underscore and file extension are not needed in the import statement - Sass understands it is a partial. Once a partial is imported into a file, all variables, mixins, and other code are available to use.
## Instructions