Skip to content
This repository was archived by the owner on Dec 4, 2017. It is now read-only.

docs(style-guide): fix some typos #1275

Closed
wants to merge 1 commit into from
Closed
Changes from all commits
Commits
File filter

Filter by extension

Filter by extension

Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
12 changes: 4 additions & 8 deletions public/docs/ts/latest/guide/style-guide.jade
Original file line number Diff line number Diff line change
Expand Up @@ -836,7 +836,7 @@ a(href="#toc") Back to top

.s-why.s-why-last
:marked
**Why?** We find this to be super important for a project. If we cannot find the files we need to work on quickly, we will not be able to work as efficiently as possible, and the structure needs to change. We may not know the file name or where its related files are, so putting them in the most intuitive locations and near each other saves a ton of time. A descriptive folder structure can help with this.
**Why?** We find this to be super important for a project. If we cannot find the files we need to work on quickly, we will not be able to work as efficiently as possible, and the structure will need to change. We may not know the file name or where its related files are, so putting them in the most intuitive locations and near each other saves a ton of time. A descriptive folder structure can help with this.

a(href="#toc") Back to top

Expand All @@ -852,15 +852,15 @@ a(href="#toc") Back to top

.s-rule.do
:marked
**Do** be descriptive with file names and keeping the contents of the file to exactly one component.
**Do** be descriptive with file names and keep the contents of the file to exactly one component.

.s-rule.avoid
:marked
**Avoid** files with multiple components, multiple services, or a mixture.

.s-why.s-why-last
:marked
**Why?** We spend less time hunting and pecking for code, and become more efficient. If this means we want longer file names, then so be it.
**Why?** We spend less time hunting for code, and become more efficient. If this means we want longer file names, then so be it.

.l-sub-section
:marked
Expand Down Expand Up @@ -1876,7 +1876,7 @@ a(href="#toc") Back to top

.s-why.s-why-last
:marked
**Why?** We avoid unintentionally not calling the hook if we misspell the method.
**Why?** We avoid unintentionally not calling the hook if we misspelled the method.

+makeExample('style-guide/ts/09-01/app/heroes/shared/hero-button/hero-button.component.avoid.ts', 'example', 'app/heroes/shared/hero-button/hero-button.component.ts')(avoid=1)
:marked
Expand Down Expand Up @@ -1920,10 +1920,6 @@ a(href="#toc") Back to top
:marked
**Why?** A component that handles routing is known as the component router, thus this follows the Angular 2 routing pattern.

.s-why
:marked
**Why?** A component that handles routing is known as the componenter router.

.s-why.s-why-last
:marked
**Why?** The `<router-outlet>` indicates where the template should be displayed for the target route.
Expand Down