Fixed quotes and updated binding diag.

manager/getting-started/features.rst

@@ -28,7 +28,7 @@ Add IIS Express From Custom Configuration File
 ----------------------------------------------
 An IIS Express server can be easily created from a custom configuration file.
 
-#. Click "File | Connect to a Server…” menu item, and a wizard starts,
+#. Click "File | Connect to a Server…" menu item, and a wizard starts,
 
    .. image:: _static/add_server_types.png
 
@@ -67,7 +67,7 @@ JetBrains Rider uses a similar approach, and it puts the configuration file at
 Jexus Manager allows you to add such a solution file as a new IIS Express
 server (so it automatically locates and reads the hidden configuration files).
 
-#. Click "File | Connect to a Server…” menu item, and a wizard starts,
+#. Click "File | Connect to a Server…" menu item, and a wizard starts,
 
    .. image:: _static/add_server_types.png
 

manager/support/licensing.rst

@@ -21,7 +21,7 @@ consequential damages.
 
 End User License Agreement
 --------------------------
-Lex Li (the “licensor”) grants you (the “licensee”) a nonexclusive license to
+Lex Li (the "licensor") grants you (the "licensee") a nonexclusive license to
 use Jexus Manager, for personal and commercial use. The licensor retains
 all intellectual ownership of Jexus Manager.
 

manager/tutorials/binding-diagnostics.rst

@@ -12,13 +12,63 @@ This page shows you how to use Binding Diagnostics.
 Background
 ----------
 IIS sites use bindings to determine what kind of incoming HTTP requests they
-would handle. However, it is usually not intuitive to know what kind of
-requests go to which binding, without learning HTTP protocol itself and how
-web browser/IIS work together.
+would handle.
+
+For example, assume that there is only a default web site right now on IIS with
+the following settings,
+
+.. code-block:: xml
+
+  <sites>
+    <site name="first" id="8">
+      <bindings>
+        <binding bindingInformation="*:80:" protocol="http" />
+      </bindings>
+      <application path="/">
+        <virtualDirectory path="/" physicalPath="e:\test1" />
+      </application>
+    </site>
+  </sites>
+
+The binding setting above ensures that all HTTP requests arriving at any of the
+network adapters of this machine are sent to this web site by HTTP.sys.
+
+And if we add a second site,
+
+.. code-block:: xml
+
+  <sites>
+    <site name="first" id="8">
+      <bindings>
+        <binding bindingInformation="*:80:" protocol="http" />
+      </bindings>
+      <application path="/">
+        <virtualDirectory path="/" physicalPath="e:\test1" />
+      </application>
+    </site>
+    <site name="second" id="8">
+      <bindings>
+        <binding bindingInformation="*:80:lextudio.com" protocol="http" />
+      </bindings>
+      <application path="/">
+        <virtualDirectory path="/" physicalPath="e:\test2" />
+      </application>
+    </site>
+  </sites>
+
+Then HTTP.sys forwards all HTTP requests with host header of "lextudio.com" to
+the second site, while all rest HTTP requests still go to the first site.
+
+It requires experience to fully understand the concepts of site bindings and
+how the HTTP request forwarding works especially when there are multiple sites
+on the same machine. Without learning HTTP protocol itself and how
+web browser/IIS work together, mistakes can be made easily.
+
+That's why Jexus Manager includes a specific diagnostics tool in this area.
 
 The Built-in Binding Diagnostics
-----------------------------------------------
-For web sites opened in Jexus Manager, there is now a Binding Diagnostics
+--------------------------------
+For a web site is opened in Jexus Manager, there is now a Binding Diagnostics
 menu item showing in the Actions panel under Troubleshooting section,
 
 .. image:: _static/bindings.png

manager/tutorials/https-binding.rst

@@ -21,20 +21,20 @@ relevant part in ``applicationHost.config`` file looks like below,
 
 .. code-block:: xml
 
-  <site name=”php” id=”8″>
+  <site name="php" id="8">
     <bindings>
-      <binding bindingInformation=”192.168.1.2:443:lextudio.com" protocol=”https” />
+      <binding bindingInformation="192.168.1.2:443:lextudio.com" protocol="https" />
     </bindings>
-    <application path=”/” applicationPool=”32bit”>
-      <virtualDirectory path=”/” physicalPath=”e:\test1” />
+    <application path="/" applicationPool="32bit">
+      <virtualDirectory path="/" physicalPath="e:\test1" />
     </application>
   </site>
-  <site name=”php” id=”8″>
+  <site name="php" id="8">
     <bindings>
-      <binding bindingInformation=”192.168.1.2:443:sharpsnmp.com” protocol=”https” />
+      <binding bindingInformation="192.168.1.2:443:sharpsnmp.com" protocol="https" />
     </bindings>
-    <application path=”/” applicationPool=”32bit”>
-      <virtualDirectory path=”/” physicalPath=”e:\test2” />
+    <application path="/" applicationPool="32bit">
+      <virtualDirectory path="/" physicalPath="e:\test2" />
     </application>
   </site>
 
@@ -86,7 +86,7 @@ binding dialog,
 
 IP Based Bindings
 -----------------
-If “Require Server Name Indication” is not checked, then this binding is not
+If "Require Server Name Indication" is not checked, then this binding is not
 SNI enabled. It also means for this binding, the certificate is registered to
 the IP address + port number (in this example, ``0.0.0.0:44300``). Windows
 stores the certificate information in a private storage for http.sys to read,

server/getting-started/install.rst

@@ -51,7 +51,7 @@ Create Default Web Site
 
 Press ``i`` on keyboard to enter edit mode.
 
-Type “Hello World from Jexus” and press Esc on keyboard to exit edit mode.
+Type "Hello World from Jexus" and press Esc on keyboard to exit edit mode.
 
 Type ``:wq`` and press Enter on keyboard to exit vi.
 

server/getting-started/upgrade.rst

@@ -17,7 +17,7 @@ Download and Unpack Jexus Files
   wget http://www.linuxdot.net/down/jexus-x.y.z.tar.gz
   tar -zxvf jexus-x.y.z.tar.gz
 
-Jexus binary package is downloaded from its official site, and extracted to a folder named “jexus-x.y.z″ after this step.
+Jexus binary package is downloaded from its official site, and extracted to a folder named "jexus-x.y.z" after this step.
 
 Stop Current Jexus Server
 -------------------------
@@ -48,9 +48,9 @@ Fix Startup Commands
 
 Press i on keyboard to enter edit mode.
 
-If previous start command “/usr/jexus/jws.start” exists, replace it with “/usr/jexus/jws start”.
+If previous start command "/usr/jexus/jws.start" exists, replace it with "/usr/jexus/jws start".
 
-Remove “/usr/jexus/state.start” if it presents.
+Remove "/usr/jexus/state.start" if it presents.
 
 Press Esc on keyboard to exit edit mode.