@@ -151,11 +151,11 @@ <h3>Sounds great!</h3>
151151 obfuscated.</ p >
152152
153153 < strong > dictionary</ strong >
154- < p > Generates identifier names using names from < code > identifiersDictionary</ code > list
154+ < p > Generates identifier names using names from < code > identifiersDictionary</ code > list.
155155 </ p >
156156
157157 < strong > hexadecimal</ strong >
158- < p > Generates random identifier names using a hexadecimal pattern (e.g: < code > 0xabc123</ code > )
158+ < p > Generates random identifier names using a hexadecimal pattern (e.g: < code > 0xabc123</ code > ).
159159 </ p >
160160
161161 < strong > mangled</ strong >
@@ -167,14 +167,14 @@ <h3>Sounds great!</h3>
167167 < tr >
168168 < td class ="collapsing "> Identifiers Dictionary</ td >
169169 < td >
170- < p > This options sets identifiers list for < code > identifierNamesGenerator: dictionary</ code > option
170+ < p > This option sets identifiers list for < code > identifierNamesGenerator: dictionary</ code > option.
171171 </ td >
172172 </ tr >
173173
174174 < tr >
175175 < td class ="collapsing "> Identifiers Prefix</ td >
176176 < td >
177- < p > This options makes all global identifiers have a specific prefix.</ p >
177+ < p > This option makes all global identifiers have a specific prefix.</ p >
178178 < p > Use this option when obfuscating multiple files that are loaded on the same page. This option
179179 helps to avoid conflicts between global identifiers of these files. Use a different prefix
180180 for each file.</ p >
@@ -585,15 +585,15 @@ <h3>Sounds great!</h3>
585585 < h3 id ="FAQ "> FAQ</ h3 >
586586
587587 < h4 > Why would I want to obfuscate my JavaScript code?</ h4 >
588- < p > There're a numerous reasons why it's a good idea to protect your code, such as:</ p >
588+ < p > There are numerous reasons why it's a good idea to protect your code, such as:</ p >
589589 < ul >
590590 < li > Prevent anyone from simply copy/pasting your work. This is specially important on 100% client side
591591 projects, such as HTML5 games;
592592 </ li >
593593 < li > Removal of comments and whitespace that aren't needed. Making it faster to load and harder to
594594 understand;
595595 </ li >
596- < li > Protection of work that hasn't been paid yet. You can show your work to the client knowing that they
596+ < li > Protection of work that hasn't been paid for yet. You can show your work to the client knowing that they
597597 won't have the source code until the invoice has been paid.
598598 </ li >
599599 </ ul >
@@ -605,11 +605,11 @@ <h4>Is this obfuscator absolutely foolproof?</h4>
605605 interpret it, so there's no way to prevent that. And any tool that promises that is not being
606606 honest.</ p >
607607
608- < h4 > Why my obfuscated code is larger than my original source?</ h4 >
608+ < h4 > Why is my obfuscated code larger than my original source?</ h4 >
609609 < p > Because the obfuscator introduces new pieces of code that are meant to protect and defend against
610610 debugging and reverse-engineering. Also strings are converted to < code > \xAB</ code > hexadecimal code to
611611 make things a little bit harder to understand. You don't have to worry too much about code size because
612- since there're a lot of repetition, the obfuscated code will be compressed extremely well by your
612+ there is a lot of repetition, so the obfuscated code will be compressed extremely well by your
613613 webserver (if you have GZIP compression enabled on your server, which most do nowadays).</ p >
614614
615615 < h4 > Can I run a minifier such as UglifyJS or Google Closure Compiler on the obfuscated output?</ h4 >
0 commit comments