8000 Fix some Grammar by Excigma · Pull Request #32 · javascript-obfuscator/javascript-obfuscator-ui · GitHub
[go: up one dir, main page]
Skip to content

Fix some Grammar #32

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Merged
merged 1 commit into from
Apr 24, 2019
Merged

Fix some Grammar #32

Changes from all commits
Commits
Show all changes
1 commit
Select commit
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
8 changes: 4 additions & 4 deletions templates/index.html
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -89,17 +89,17 @@ <h3>What is this?</h3>
functionality of the original code.</p>
</div>
<div class="column">
<h3>So, like UglifyJS, Closure Compiler, etc?</h3>
<h3>So, it is like UglifyJS, Closure Compiler, etc?</h3>
<p>Yes and no. While UglifyJS (and others minifiers) does make the output code harder to understand
(compressed and ugly), it can be easily be transformed into something readable using a JS
Beautifier.</p>
<p>This tool prevents that by using various transformations and "traps", such as
5D93 <strong>self-defending</strong> and <strong>debug protection</strong>.</p>
</div>
<div class="column">
<h3>How does the obfuscation works?</h3>
<p>Through a series of transformations, such as variable / function / arguments renaming, strings removal,
and others, your source code is transformed into something unreadable, while working exatcly as
<h3>How does the obfuscation work?</h3>
<p>Through a series of transformations, such as variable / function / arguments renaming, string removal,
and others, your source code is transformed into something unreadable, while working exactly as
before.</p>
<p><a href="#FAQ">Read more in the FAQ...</a></p>
</div>
Expand Down
0