Summary Files Commits Branches @commit @diff @stats
path: root / docs / getting-started.html
diff options
context:
space:
mode:
Commit4a723077b118980c5fd399d77bbc1a120eed559e (patch)
Author
 Neil Panchal <neilpanchal@gmail.com>
2017-12-17 18:58:02 -0700
Committer
 GitHub <noreply@github.com>
2017-12-17 18:58:02 -0700
Files7a088e4dd72aea6d2c6f422f51676c394f6d911a /docs/getting-started.html
Spectre-Dark-Gruvbox-4a723077b118980c5fd399d77bbc1a120eed559e.tar
Spectre-Dark-Gruvbox-4a723077b118980c5fd399d77bbc1a120eed559e.tar.gz
Spectre-Dark-Gruvbox-4a723077b118980c5fd399d77bbc1a120eed559e.zip
Parent4a784e66ed171336e9b9b281e02c2fdff2bde8cd (diff)
Corrected typo in getting-started.html
Section "Importing Sass". Changed "custom" to "customize".
1 files changed, 1 insertions, 1 deletions
-rw-r--r--docs/getting-started.html2
diff --git a/docs/getting-started.html b/docs/getting-started.html
index d00760d..10a45a5 100644
--- a/docs/getting-started.html
+++ b/docs/getting-started.html
@@ -389,7 +389,7 @@
</div>
<h4 id="importing" class="s-subtitle">Importing Sass</h4>
<div class="docs-note">
- <p>It is recommended to custom Spectre by importing Sass source files to your projects. In this way, you can keep Spectre up to date without conflicts, since Spectre code and your custom code are separate.</p>
+ <p>It is recommended to customize Spectre by importing Sass source files to your projects. In this way, you can keep Spectre up to date without conflicts, since Spectre code and your custom code are separate.</p>
<ul>
<li>First, create your own project and install Spectre via <a href="#installation">NPM or other package managers</a>.</li>
<li>Then create your <code>project-name.scss</code> file in the root folder. You can use <code>project-name.scss</code> to define your variables.</li>