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-Note that the underscore is not needed in the
@import 'mixins'
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