update page

README.md

@@ -61,10 +61,10 @@ Usage:
   * Besides that, four bookmarks are added to the "Bookmarks Toolbar," which
    will take you to visit your Java I2P applications, or the "Simplified I2P
    Landing Page" embedded in the plugin:
-  * ![Landing page](lander.png)
+   - ![Landing page](lander.png)
   * Also, there's a menu for accessing I2P functionality while you're browsing.
    It lets you control a few settings in a granular way.
-  * ![Menu](menu.png)
+   - ![Menu](menu.png)
   * You can re-enable WebRTC but force it to always use the proxy that is
    enforced by the tab.
   * You can either force the browser to delete all history for I2P sites
@@ -80,10 +80,10 @@ Usage:
    to the I2P container. Isolate the router console from other local
    applications by automatically intercepting requests to the router console to
    another container.
-  * ![Visiting i2p-projekt.i2p](i2psetproxy.js.png)
+   - ![Visiting i2p-projekt.i2p](i2psetproxy.js.png)
   * [done] **Indicate** the I2P browser is in use visually. Find an
    acceptable way to indicate it on Android.
-  * ![Visiting webmail](susimail.png)
+   - ![Visiting webmail](susimail.png)
   * [done] **Set** the http proxy to use the local I2P proxy automatically.
    Provide specific configuration for other types of I2P proxies(SOCKS,
    isolating HTTP)
@@ -91,7 +91,7 @@ Usage:
    them with the proxy enforced.
   * [done] **Change** the color of the browser window to indicate that I2P is in
    use
-  * ![Visiting i2ptunnel](i2ptunnel.png)
+   - ![Visiting i2ptunnel](i2ptunnel.png)
   * [ready/broken/wip] **Provide** help in a variety of languages.
   * [wip] **Monitor** the health and readiness of the I2P router it is
    instructed to use. Currently the plugin checks whether the HTTP Proxy is
@@ -103,12 +103,12 @@ Usage:
    confined to it's own container tab. (2) Use a custom protocol handler to
    place each i2p application/plugin under it's own origin, shortening router
    console URL's and placing applications under their own origin.
-  * ![Visiting routerconsole](routerconsole.png)
+   - ![Visiting routerconsole](routerconsole.png)
   * [wip] **Handle Torrents** by talking to i2psnark-rpc plugin and then
    adding them directly into the Firefox downloads drop-downs, menus, etc. If I
    can. Right now instead of talking to snark-rpc, it uses a web-based protocl
    handler that simply auto-fills the torrent into i2psnark.
-  * ![Visiting i2psnark](i2psnark.png)
+   - ![Visiting i2psnark](i2psnark.png)
   * [barely started] **Isolate** traffic by contextual identity to it's own HTTP
    Proxy tunnel, each reflecting it's own pseudonymous identity within I2P. The
    contextual identities. For now, the contextual identities used to manage
@@ -124,7 +124,7 @@ Usage:
     tunnel-close timeout and key-reuse until specifically invoked.
     - I2P Blogging: Use this for posting content to the web interface of your
     blog or to other similar websites that you create content on.
-  * ![Visiting clearweb](clearweb.png)
+   - ![Visiting clearweb](clearweb.png)
 
 ### Video
 

index.html

@@ -68,11 +68,15 @@ domain will automatically stop the current tab and re-open the I2P site in an
 I2P Browser tab.</li>
 <li>Besides that, four bookmarks are added to the "Bookmarks Toolbar," which
 will take you to visit your Java I2P applications, or the "Simplified I2P
-Landing Page" embedded in the plugin:</li>
+Landing Page" embedded in the plugin:
+<ul>
 <li><img src="lander.png" alt="Landing page" title="" /></li>
+</ul></li>
 <li>Also, there's a menu for accessing I2P functionality while you're browsing.
-It lets you control a few settings in a granular way.</li>
+It lets you control a few settings in a granular way.
+<ul>
 <li><img src="menu.png" alt="Menu" title="" /></li>
+</ul></li>
 <li>You can re-enable WebRTC but force it to always use the proxy that is
 enforced by the tab.</li>
 <li>You can either force the browser to delete all history for I2P sites
@@ -89,19 +93,25 @@ administer I2P</li>
 (container). Intercept requests to .i2p domains and automatically route them
 to the I2P container. Isolate the router console from other local
 applications by automatically intercepting requests to the router console to
-another container.</li>
+another container.
+<ul>
 <li><img src="i2psetproxy.js.png" alt="Visiting i2p-projekt.i2p" title="" /></li>
+</ul></li>
 <li>[done] <strong>Indicate</strong> the I2P browser is in use visually. Find an
-acceptable way to indicate it on Android.</li>
+acceptable way to indicate it on Android.
+<ul>
 <li><img src="susimail.png" alt="Visiting webmail" title="" /></li>
+</ul></li>
 <li>[done] <strong>Set</strong> the http proxy to use the local I2P proxy automatically.
 Provide specific configuration for other types of I2P proxies(SOCKS,
 isolating HTTP)</li>
 <li>[done] <strong>Disable</strong> risky webRTC features/offer the option to re-enable
 them with the proxy enforced.</li>
 <li>[done] <strong>Change</strong> the color of the browser window to indicate that I2P is in
-use</li>
+use
+<ul>
 <li><img src="i2ptunnel.png" alt="Visiting i2ptunnel" title="" /></li>
+</ul></li>
 <li>[ready/broken/wip] <strong>Provide</strong> help in a variety of languages.</li>
 <li>[wip] <strong>Monitor</strong> the health and readiness of the I2P router it is
 instructed to use. Currently the plugin checks whether the HTTP Proxy is
@@ -112,13 +122,17 @@ inert at this time.</li>
 within their own contextual identity. (1) The router console is automatically
 confined to it's own container tab. (2) Use a custom protocol handler to
 place each i2p application/plugin under it's own origin, shortening router
-console URL's and placing applications under their own origin.</li>
+console URL's and placing applications under their own origin.
+<ul>
 <li><img src="routerconsole.png" alt="Visiting routerconsole" title="" /></li>
+</ul></li>
 <li>[wip] <strong>Handle Torrents</strong> by talking to i2psnark-rpc plugin and then
 adding them directly into the Firefox downloads drop-downs, menus, etc. If I
 can. Right now instead of talking to snark-rpc, it uses a web-based protocl
-handler that simply auto-fills the torrent into i2psnark.</li>
+handler that simply auto-fills the torrent into i2psnark.
+<ul>
 <li><img src="i2psnark.png" alt="Visiting i2psnark" title="" /></li>
+</ul></li>
 <li>[barely started] <strong>Isolate</strong> traffic by contextual identity to it's own HTTP
 Proxy tunnel, each reflecting it's own pseudonymous identity within I2P. The
 contextual identities. For now, the contextual identities used to manage
@@ -135,8 +149,8 @@ where your identity is behaviorally linkable. This has a very long
 tunnel-close timeout and key-reuse until specifically invoked.</li>
 <li>I2P Blogging: Use this for posting content to the web interface of your
 blog or to other similar websites that you create content on.</li>
-</ul></li>
 <li><img src="clearweb.png" alt="Visiting clearweb" title="" /></li>
+</ul></li>
 </ul>
 
 <h3>Video</h3>