linuxdcpp-team team mailing list archive

[noreply@xxxxxxxxxxxxx]

------------------------------------------------------------
revno: 2555
committer: eMTee <emtee11@xxxxxxxxx>
branch nick: dcplusplus
timestamp: Mon 2011-06-13 19:46:39 +0200
message:
  fix html syntax
modified:
  help/settings_connectivity_manual.html


--
lp:dcplusplus
https://code.launchpad.net/~dcplusplus-team/dcplusplus/trunk

Your team Dcplusplus-team is subscribed to branch lp:dcplusplus.
To unsubscribe from this branch go to https://code.launchpad.net/~dcplusplus-team/dcplusplus/trunk/+edit-subscription

=== modified file 'help/settings_connectivity_manual.html'
--- help/settings_connectivity_manual.html	2011-04-11 20:39:22 +0000
+++ help/settings_connectivity_manual.html	2011-06-13 17:46:39 +0000
@@ -104,13 +104,13 @@
 <p cshelp="IDH_SETTINGS_CONNECTIVITY_MAPPER">
 DC++ has several interfaces available it can use to try to automatically map the ports it requires
 on the router:
-<li>
-<ul>NAT-PMP: A lightweight protocol that is not widely used by generic routers; but open-source
-	firmwares generally implement it.</ul>
-<ul>MiniUPnP: An open-source UPnP library.</ul>
-<ul>Windows UPnP: Use Windows discovery services. Note that the DC++ implementation of Windows UPnP
-	is partial and prone to random failures. MiniUPnP is recommended instead.</ul>
-</li>
+<ul>
+<li>NAT-PMP: A lightweight protocol that is not widely used by generic routers; but open-source
+	firmwares generally implement it.</li>
+<li>MiniUPnP: An open-source UPnP library.</li>
+<li>Windows UPnP: Use Windows discovery services. Note that the DC++ implementation of Windows UPnP
+	is partial and prone to random failures. MiniUPnP is recommended instead.</li>
+</ul>
 The interface selected here will be tried first; other available interfaces will then be tried if
 the preferred port mapping interface were to fail.
 </p>