@@ -169,11 +169,11 @@ <h3>Sounds great!</h3>
169
169
obfuscated.</ p >
170
170
171
171
< strong > dictionary</ strong >
172
- < p > Generates identifier names using names from < code > identifiersDictionary</ code > list
172
+ < p > Generates identifier names using names from < code > identifiersDictionary</ code > list.
173
173
</ p >
174
174
175
175
< strong > hexadecimal</ strong >
176
- < p > Generates random identifier names using a hexadecimal pattern (e.g: < code > 0xabc123</ code > )
176
+ < p > Generates random identifier names using a hexadecimal pattern (e.g: < code > 0xabc123</ code > ).
177
177
</ p >
178
178
179
179
< strong > mangled</ strong >
@@ -185,14 +185,14 @@ <h3>Sounds great!</h3>
185
185
< tr >
186
186
< td class ="collapsing "> Identifiers Dictionary</ td >
187
187
< td >
188
- < p > This options sets identifiers list for < code > identifierNamesGenerator: dictionary</ code > option
188
+ < p > This option sets identifiers list for < code > identifierNamesGenerator: dictionary</ code > option.
189
189
</ td >
190
190
</ tr >
191
191
192
192
< tr >
193
193
< td class ="collapsing "> Identifiers Prefix</ td >
194
194
< td >
195
- < p > This options makes all global identifiers have a specific prefix.</ p >
195
+ < p > This option makes all global identifiers have a specific prefix.</ p >
196
196
< p > Use this option when obfuscating multiple files that are loaded on the same page. This option
197
197
helps to avoid conflicts between global identifiers of these files. Use a different prefix
198
198
for each file.</ p >
@@ -607,15 +607,15 @@ <h3>Sounds great!</h3>
607
607
< h3 id ="FAQ "> FAQ</ h3 >
608
608
609
609
< h4 > Why would I want to obfuscate my JavaScript code?</ h4 >
610
- < p > There're a numerous reasons why it's a good idea to protect your code, such as:</ p >
610
+ < p > There are numerous reasons why it's a good idea to protect your code, such as:</ p >
611
611
< ul >
612
612
< li > Prevent anyone from simply copy/pasting your work. This is specially important on 100% client side
613
613
projects, such as HTML5 games;
614
614
</ li >
615
615
< li > Removal of comments and whitespace that aren't needed. Making it faster to load and harder to
616
616
understand;
617
617
</ li >
618
- < li > Protection of work that hasn't been paid yet. You can show your work to the client knowing that they
618
+ < li > Protection of work that hasn't been paid for yet. You can show your work to the client knowing that they
619
619
won't have the source code until the invoice has been paid.
620
620
</ li >
621
621
</ ul >
@@ -627,11 +627,11 @@ <h4>Is this obfuscator absolutely foolproof?</h4>
627
627
interpret it, so there's no way to prevent that. And any tool that promises that is not being
628
628
honest.</ p >
629
629
630
- < h4 > Why my obfuscated code is larger than my original source?</ h4 >
630
+ < h4 > Why is my obfuscated code larger than my original source?</ h4 >
631
631
< p > Because the obfuscator introduces new pieces of code that are meant to protect and defend against
632
632
debugging and reverse-engineering. Also strings are converted to < code > \xAB</ code > hexadecimal code to
633
633
make things a little bit harder to understand. You don't have to worry too much about code size because
634
- since there're a lot of repetition, the obfuscated code will be compressed extremely well by your
634
+ there is a lot of repetition, so the obfuscated code will be compressed extremely well by your
635
635
webserver (if you have GZIP compression enabled on your server, which most do nowadays).</ p >
636
636
637
637
< h4 > Can I run a minifier such as UglifyJS or Google Closure Compiler on the obfuscated output?</ h4 >
0 commit comments