fix(aio): contributor.html typos
This commit is contained in:
Ward Bell
Alex Rickabaugh
parent
7c2ce296d3
commit
5c38012980
|
|
@ -100,16 +100,16 @@
|
||||||
<p>When not specified, Angular is assumed to be referring to the latest and greatest stable version from the Angular Team.</p>
|
<p>When not specified, Angular is assumed to be referring to the latest and greatest stable version from the Angular Team.</p>
|
||||||
|
|
||||||
<h4>Example</h4>
|
<h4>Example</h4>
|
||||||
<p><b>Version 4.1 Now Available</b> - We are pleased to announce that the latest release of Angular is now available. Staying up to date is easy!</p>
|
<p><b>Version v4.1 now available</b> - We are pleased to announce that the latest release of Angular is now available. Staying up to date is easy!</p>
|
||||||
|
|
||||||
<h4>Example</h4>
|
<h4>Example</h4>
|
||||||
<p><b>Correct</b></p>
|
<p><b>Correct</b></p>
|
||||||
|
|
||||||
<p><b>New *ngIf Capabilities</b> - New in version 4.0 is the ability to use additional syntax to create local variables. This can be very helpful in cases such as working with observables …</p>
|
<p><b>New <code>*ngIf</code> capabilities</b> - New in version 4.0 is the ability to use additional syntax to create local variables. This can be very helpful in cases such as working with observables …</p>
|
||||||
|
|
||||||
<p><b>Incorrect</b></p>
|
<p><b>Incorrect</b></p>
|
||||||
|
|
||||||
<p><b>New *ngIf Capabilities In Angular 4</b> - Angular 4 introduces the ability to use additional syntax to create local variables. This can be very helpful in cases such as working with observables …</p>
|
<p><b>New <code>*ngIf</code> capabilities in Angular v4</b> - Angular v4 introduces the ability to use additional syntax to create local variables. This can be very helpful in cases such as working with observables …</p>
|
||||||
|
|
||||||
<p><b>Reasoning</b></p>
|
<p><b>Reasoning</b></p>
|
||||||
|
|
||||||
|
|
@ -117,7 +117,7 @@
|
||||||
|
|
||||||
<h3>AngularJS</h3>
|
<h3>AngularJS</h3>
|
||||||
|
|
||||||
<p><b>AngularJS</b> is the 1.x series of work and promises provided by the Angular team.</p>
|
<p><b>AngularJS</b> is the v1.x series of work and promises provided by the Angular team.</p>
|
||||||
|
|
||||||
<h4>Examples</h4>
|
<h4>Examples</h4>
|
||||||
<ol>
|
<ol>
|
||||||
|
|
@ -144,7 +144,8 @@
|
||||||
|
|
||||||
<h3>3rd Party Projects</h3>
|
<h3>3rd Party Projects</h3>
|
||||||
|
|
||||||
<b>X for Angular</b>
|
<p><b>X for Angular</b></p>
|
||||||
|
|
||||||
<p>3rd parties should use the terminology “X for Angular” or “ng-X” for software projects. Projects should avoid the use of Angular X (e.g. Angular UI Toolkit), as it could create authorship confusion. This rule does not apply to events or meetup groups.</p>
|
<p>3rd parties should use the terminology “X for Angular” or “ng-X” for software projects. Projects should avoid the use of Angular X (e.g. Angular UI Toolkit), as it could create authorship confusion. This rule does not apply to events or meetup groups.</p>
|
||||||
|
|
||||||
<p>Developers should avoid using Angular version numbers in project names, as this will artificially limit their projects by tying them to a point in time of Angular, or will require renaming over time.</p>
|
<p>Developers should avoid using Angular version numbers in project names, as this will artificially limit their projects by tying them to a point in time of Angular, or will require renaming over time.</p>
|
||||||
|
|
@ -153,24 +154,24 @@
|
||||||
|
|
||||||
<b>Do not use</b>
|
<b>Do not use</b>
|
||||||
<ul>
|
<ul>
|
||||||
<li>ng2-</li>
|
<li><code>ng2-</code></li>
|
||||||
<li>angular2-</li>
|
<li><code>angular2-</code></li>
|
||||||
</ul>
|
</ul>
|
||||||
|
|
||||||
<b>OK to use</b>
|
<b>OK to use</b>
|
||||||
<ul>
|
<ul>
|
||||||
<li>ng-</li>
|
<li><code>ng-</code></li>
|
||||||
<li>angular-</li>
|
<li><code>angular-</code></li>
|
||||||
</ul>
|
</ul>
|
||||||
|
|
||||||
<p>As always, component and directive selectors should not begin with “ng-” selectors as this will conflict with components and directives provided by the Angular team.</p>
|
<p>As always, component and directive selectors should not begin with “ng-” selectors as this will conflict with components and directives provided by the Angular team.</p>
|
||||||
|
|
||||||
<h4>Examples</h4>
|
<h4>Examples</h4>
|
||||||
<ul>
|
<ul>
|
||||||
<li>The ng-BE team just launched ng-health to help developers track their own health.</li>
|
<li>The ng-BE team just launched <code>ng-health</code> to help developers track their own health.</li>
|
||||||
<li>I’m going to use NativeScript for Angular to take advantage of native UI widgets.</li>
|
<li>I’m going to use NativeScript for Angular to take advantage of native UI widgets.</li>
|
||||||
<li>ReallyCoolTool for Angular.</li>
|
<li><code>ReallyCoolTool</code> for Angular.</li>
|
||||||
<li>ReallyCoolTool for AngularJS.</li>
|
<li><code>ReallyCoolTool</code> for AngularJS.</li>
|
||||||
</ul>
|
</ul>
|
||||||
</div>
|
</div>
|
||||||
</div>
|
</div>
|
||||||
|
|
@ -185,8 +186,8 @@
|
||||||
but we want to remain consistent on the styling and use of them to prevent confusion and to appear unified.
|
but we want to remain consistent on the styling and use of them to prevent confusion and to appear unified.
|
||||||
</p>
|
</p>
|
||||||
<ul>
|
<ul>
|
||||||
<li>Ahead of Time Compilation (AOT)</li>
|
<li>Ahead of Time compilation (AOT)</li>
|
||||||
<li>Just in Time Compilation (JIT)</li>
|
<li>Just in Time compilation (JIT)</li>
|
||||||
</ul>
|
</ul>
|
||||||
</div>
|
</div>
|
||||||
</div>
|
</div>
|
||||||
|
|
|
||||||
Loading…
Reference in New Issue