Summary Files Commits Branches @commit @diff @stats
path: root / docs / getting-started.html
diff options
context:
space:
mode:
Commit0a0062616a8ce0e0ef801c542d31f426650f3841 (patch)
Author
 Yan Zhu <picturepan2@hotmail.com>
2017-12-18 16:58:13 +0800
Committer
 GitHub <noreply@github.com>
2017-12-18 16:58:13 +0800
Files59f855cb86f6925befabe42975e7fd1c9c7e7400 /docs/getting-started.html
Spectre-Dark-Gruvbox-0a0062616a8ce0e0ef801c542d31f426650f3841.tar
Spectre-Dark-Gruvbox-0a0062616a8ce0e0ef801c542d31f426650f3841.tar.gz
Spectre-Dark-Gruvbox-0a0062616a8ce0e0ef801c542d31f426650f3841.zip
Parent14e581de8c8b5610abf12cd71a46e5663bf341e8 (diff)
Parent4a723077b118980c5fd399d77bbc1a120eed559e (diff)
Merge pull request #368 from neilpanchal/patch-1
Corrected typo in getting-started.html
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>