From 994131c61e01ffe661e8b1e86798152975619d69 Mon Sep 17 00:00:00 2001
From: Jerry Zhao <jchao@y7mail.com>
Date: Sun, 21 Jun 2015 19:37:23 +1000
Subject: [PATCH] escape <script>

---
 en/09.3.md | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)

diff --git a/en/09.3.md b/en/09.3.md
index 406e3afd..178c7692 100644
--- a/en/09.3.md
+++ b/en/09.3.md
@@ -19,7 +19,7 @@ XSS present the main means and ends as follows:
 
 ## XSS principles
 
-Web applications that return requested data to users without first inspecting and filtering it can allow malicious users to inject scripts (typically embedded inside HTML within <script> tags) onto other users' browsers. When this malicious code is rendered on a user's browser without first having been escaped from, the user's browser will interpret this code: this is the definition of an XSS attack, and this type of mistake is the leading cause of XSS vulnerabilities.
+Web applications that return requested data to users without first inspecting and filtering it can allow malicious users to inject scripts (typically embedded inside HTML within `<script>` tags) onto other users' browsers. When this malicious code is rendered on a user's browser without first having been escaped from, the user's browser will interpret this code: this is the definition of an XSS attack, and this type of mistake is the leading cause of XSS vulnerabilities.
 
 Let's go through the process of a reflective XSS attack. Let's say there's a website that outputs a user's name according to the URL query parameters; access the following URL `http://127.0.0.1/?name=astaxie` will cause the server to output the following: