Skip to content
This repository

HTTPS clone URL

Subversion checkout URL

You can clone with HTTPS or Subversion.

Download ZIP

Spelling/grammar corrections #6

Merged
merged 1 commit into from almost 3 years ago

2 participants

Evan Shaw Tait Brown
Evan Shaw
edsrzf commented May 05, 2011

Thanks for writing this. I corrected a few small spelling/grammars I found while reading it.

Tait Brown
Owner
taitems commented May 11, 2011

Some overzealous corrections will need to be undone but I'll just merge the whole thing.

Tait Brown taitems merged commit bbd3b2d into from May 11, 2011
Tait Brown taitems closed this May 11, 2011
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Showing 1 unique commit by 1 author.

May 05, 2011
Evan Shaw Spelling/grammar corrections 841deb5
This page is out of date. Refresh to see the latest.

Showing 1 changed file with 15 additions and 15 deletions. Show diff stats Hide diff stats

  1. 30  index.html
30  index.html
@@ -129,7 +129,7 @@
129 129
 			<h2>Images Need &lsquo;Alt&rsquo; Text</h2>
130 130
 			
131 131
 			<p>
132  
-				The <code>&lt;img&gt;</code> tag requires <code>alt</code> text to both validate and meet accessibility guidelines. The text in the <code>alt</code> attribute should be descriptive of what the image shows, or is trying to achieve, unless of the course the image is not critical. 
  132
+				The <code>&lt;img&gt;</code> tag requires <code>alt</code> text to both validate and meet accessibility guidelines. The text in the <code>alt</code> attribute should be descriptive of what the image shows, or is trying to achieve, unless of course the image is not critical. 
133 133
 			</p>
134 134
 			<p>
135 135
 				If the image is of a list bullet or other trivial icons, it is recommended to simply leave the <code>alt</code> attribute empty, but still present. A screenreader will then ignore it, as opposed to having to read out "bullet" 20 times.
@@ -250,7 +250,7 @@
250 250
 				}
251 251
 			]]></script>
252 252
 			
253  
-			<h3>Always Using Parenthesis</h3>
  253
+			<h3>Always Using Braces</h3>
254 254
 			
255 255
 			<script type="syntaxhighlighter" class="brush: js;  toolbar: false; gutter: false;"><![CDATA[
256 256
 				// Bad
@@ -277,7 +277,7 @@
277 277
 			<h2>Commenting</h2>
278 278
 			
279 279
 			<p>
280  
-				Javascript code requires regular commenting in order to make it easily understandable. The general rule of thumb for javascript is to use single line comments where possible to
  280
+				JavaScript code requires regular commenting in order to make it easily understandable. The general rule of thumb for JavaScript is to use single line comments where possible to
281 281
 				quickly and concisely describe what a particular line or block of code is meant to do. If you need to be a little more descriptive eg, describing what a function is meant to do,
282 282
 				then the long comment syntax is better.
283 283
 			</p>
@@ -305,8 +305,8 @@
305 305
 			<h2>Always Use === Comparison</h2>
306 306
 			
307 307
 			<p>
308  
-				The use of the == equality operator allows for frustrating bugs to slip through almost undetected. It allows for weak typing that is best explained by <a href="http://bonsaiden.github.com/JavaScript-Garden/#types.equality" target="_blank">Javascript Garden</a>.
309  
-				The use of the strict equality operator === does not run type coercion and therefore strictly evaluates the difference between two objects. Again, consult <a href="http://bonsaiden.github.com/JavaScript-Garden/#types.equality" target="_blank">Javascript Garden</a> for more information
  308
+				The use of the == equality operator allows for frustrating bugs to slip through almost undetected. It allows for weak typing that is best explained by <a href="http://bonsaiden.github.com/JavaScript-Garden/#types.equality" target="_blank">JavaScript Garden</a>.
  309
+				The use of the strict equality operator === does not run type coercion and therefore strictly evaluates the difference between two objects. Again, consult <a href="http://bonsaiden.github.com/JavaScript-Garden/#types.equality" target="_blank">JavaScript Garden</a> for more information
310 310
 			</p>
311 311
 			<script type="syntaxhighlighter" class="brush: js;  toolbar: false; gutter: false;"><![CDATA[
312 312
 				var zeroAsAString = "0";
@@ -708,7 +708,7 @@
708 708
 			
709 709
 			<script type="syntaxhighlighter" class="brush: js;  toolbar: false; gutter: false;"><![CDATA[
710 710
 				if ($.browser.msie) {
711  
-					// no it doesnt
  711
+					// no it doesn�t
712 712
 				}				
713 713
 			]]></script>
714 714
 			
@@ -728,7 +728,7 @@
728 728
 			<p>
729 729
 				In steps <a href="http://www.modernizr.com" target="_blank">Modernizr</a>, a JavaScript library developed in part by industry dream-boat Paul Irish. 
730 730
 				With wide adoption, tiny file-size and plenty of <a href="http://www.modernizr.com/docs/#s1" target="_blank">documentation</a>: implementing it is a no-brainer. 
731  
-				It creates a <code>Modernizr</code> object that contains the results of it's detection tests, so checking feature support is as simple as the following:
  731
+				It creates a <code>Modernizr</code> object that contains the results of its detection tests, so checking feature support is as simple as the following:
732 732
 			</p>
733 733
 			
734 734
 			<script type="syntaxhighlighter" class="brush: js;  toolbar: false; gutter: false;"><![CDATA[
@@ -765,7 +765,7 @@
765 765
 			<h2>Chain Like a Sick Bitch</h2>
766 766
 			
767 767
 			<p>
768  
-				One of the best parts of jQuery is it's function chaining. You've probably used it a bit, maybe a few simple calls... but have you ever traversed the DOM like a sick bitch? Take some time to familiarise yourself with the <a href="http://api.jquery.com/end/" target="_blank">.end()</a> function. It is critical for when you begin stepping up and down the DOM tree from your original selector.
  768
+				One of the best parts of jQuery is its function chaining. You've probably used it a bit, maybe a few simple calls... but have you ever traversed the DOM like a sick bitch? Take some time to familiarise yourself with the <a href="http://api.jquery.com/end/" target="_blank">.end()</a> function. It is critical for when you begin stepping up and down the DOM tree from your original selector.
769 769
 			</p>
770 770
 			
771 771
 			<script type="syntaxhighlighter" class="brush: js;  toolbar: false; gutter: false;"><![CDATA[
@@ -800,7 +800,7 @@
800 800
 			
801 801
 			<p>
802 802
 				When using <code>$.animate</code>, <code>queue: false</code> can be added to the parameters to prevent chaining. Animation shortcuts such as <code>$.fadeIn</code> or <code>$.slideDown</code> do not take <code>queue</code> settings.
803  
-				Instead you have to pre-empt these animations with the <code>$.stop</code> method of pausing currently executing animations. Certain scenarios require the animation to stop dead in it's tracks, or to jump to the end of the transition. 
  803
+				Instead you have to pre-empt these animations with the <code>$.stop</code> method of pausing currently executing animations. Certain scenarios require the animation to stop dead in its tracks, or to jump to the end of the transition. 
804 804
 				It is recommended you familiarise yourself with the <a href="http://api.jquery.com/stop/" target="_blank">documentation</a> of the parameters <code>clearQueue</code> and <code>jumpToEnd</code>, because god knows I can't help you there.
805 805
 			</p>
806 806
 			
@@ -833,7 +833,7 @@
833 833
 			
834 834
 			<p>
835 835
 				jQuery is pretty chill. It can do pretty much everything but make you coffee, and I hear that's in the roadmap for 2.0. One thing you have to be careful about is abusing the power that is the <a href="http://sizzlejs.com/" target="_blank">sizzleJS</a> selector engine.
836  
-				There are two strategies to overcome this: <em>caching the selectors results</em> and <em>using efficient selectors</em>.
  836
+				There are two strategies to overcome this: <em>caching the selector results</em> and <em>using efficient selectors</em>.
837 837
 			</p>
838 838
 			
839 839
 			<h3>Caching Selector Results</h3>
@@ -1032,7 +1032,7 @@
1032 1032
 			<h3>From 0px to Hero</h3>
1033 1033
 			
1034 1034
 			<p>
1035  
-				Assigning a unit type to a properties value of zero is redundant. It is not important to know whether an element should be <code>0px</code> from the left or <code>0 elephants</code> from the left, just that it's bang on the left.
  1035
+				Assigning a unit type to a property value of zero is redundant. It is not important to know whether an element should be <code>0px</code> from the left or <code>0 elephants</code> from the left, just that it's bang on the left.
1036 1036
 			</p>
1037 1037
 			
1038 1038
 			<script type="syntaxhighlighter" class="brush: css;  toolbar: false; gutter: false;"><![CDATA[
@@ -1057,10 +1057,10 @@
1057 1057
 		
1058 1058
 		
1059 1059
 		<div class="entry">
1060  
-			<h2>Clearing floats</h2>
  1060
+			<h2>Clearing Floats</h2>
1061 1061
 			
1062 1062
 			<p>
1063  
-				Clearing a <code>&lt;div&gt;</code> used to mean extra DOM, because it involved adding an extra clearer element. The better way is to set a specific width on the parent element (it doesn't work if it's "auto") and an overflow value of either auto or hidden. 
  1063
+				Clearing a <code>&lt;div&gt;</code> used to mean extra DOM, because it involved adding an extra clearer element. The better way is to set a specific width on the parent element (it doesn't work if its "auto") and an overflow value of either auto or hidden. 
1064 1064
 				"Hidden" obviously degrades better, but there are some IE compatibility versions where auto works better.
1065 1065
 			</p>
1066 1066
 			
@@ -1130,8 +1130,8 @@
1130 1130
 			<h2>You're Not !important</h2>
1131 1131
 			
1132 1132
 			<p>
1133  
-				A reliance upon the <code>!important</code> tag is a dangerous thing. The cases that warrent its use are rare and specific. They revolve around the necessity to override another stylesheet which you do not have access or permission to edit.
1134  
-				Another scenario is hard coding an element's styles to prevent inline JavaScript styles from taking precedence. Instead <code>!important</code> is used a lazy shortcut to set the priority of your style over another, causing headaches further down the line.
  1133
+				A reliance upon the <code>!important</code> tag is a dangerous thing. The cases that warrant its use are rare and specific. They revolve around the necessity to override another stylesheet which you do not have access or permission to edit.
  1134
+				Another scenario is hard coding an element's styles to prevent inline JavaScript styles from taking precedence. Instead <code>!important</code> is used as a lazy shortcut to set the priority of your style over another, causing headaches further down the line.
1135 1135
 			</p>
1136 1136
 			
1137 1137
 			<p>
Commit_comment_tip

Tip: You can add notes to lines in a file. Hover to the left of a line to make a note

Something went wrong with that request. Please try again.