fix formatting error and remove duplicate links

diff --git a/docs/howtos/HowToPkgsrc.mdwn b/docs/howtos/HowToPkgsrc.mdwn
index 9824f2a..dbfe03e 100644 (file)
--- a/docs/howtos/HowToPkgsrc.mdwn
+++ b/docs/howtos/HowToPkgsrc.mdwn
@@ -1,8 +1,10 @@
-[[!toc levels=2 ]]
+# pkgsrc on DragonFly
 
 The following page describes the basics of the pkgsrc system as used by DragonFly.
 
-## pkgsrc Overview 
+[[!toc levels=2 ]]
+
+## Overview 
 
 ### History 
 [Pkgsrc](http://www.pkgsrc.org) is a packaging system that was originally created for NetBSD. It has been ported to DragonFly, along with other operating systems.  Pkgsrc is very similar to FreeBSD's ports mechanism.
@@ -136,7 +138,7 @@ from the `/usr/pkgsrc` directory.
 
 It's also possible to browse website that show all the available pkgsrc packages, such as [http://pkgsrc.se/](http://pkgsrc.se) .
 
-### Installing packages from source
+### Installing applications from source
 
 Packages are built by going into the appropriate directory and issuing `bmake install clean`. For example, to build the *screen* package you need to issue the following commands.
 
@@ -187,7 +189,7 @@ It is possible that you see a warning when installing binary packages on a DEVEL
 
 You can safely ignore this warning.  Normally all packages build for RELEASE run fine on DEVELOPMENT unless a major API-breakage was introduced.  In this case you would see a message from the developers on the appropriate mailing list.
 
-### List all installed packages 
+### List all installed applications 
 
 To obtain a list of all the packages that are installed on your system:
 
@@ -273,7 +275,7 @@ Packages often install rc.d scripts to control software running on startup.  To
     RCD_SCRIPTS_DIR=/etc/rc.d
     PKG_RCD_SCRIPTS=YES
 
-This option can be set in the environment to activate it for binary packages.  These packages will still have to be enabled in `/etc/rc.conf/ to run at boot.  If these options aren't set, the rc file will be placed in `/usr/pkg/share/examples/rc.d/` and will need to be manually copied over to `/etc/rc.d`.
+This option can be set in the environment to activate it for binary packages.  These packages will still have to be enabled in `/etc/rc.conf/` to run at boot.  If these options aren't set, the rc file will be placed in `/usr/pkg/share/examples/rc.d/` and will need to be manually copied over to `/etc/rc.d`.
 
 Many other options can be set in this file; see `/usr/pkgsrc/mk/defaults/mk.conf` for examples.
 
@@ -298,7 +300,6 @@ Once you have identified where the application's manual pages have been installe
 
     # pkg_info foopackage-1.0.0
 
-  
 A `WWW:` line, if present, should provide a URL for the application's web site.
 
 ### Dealing with Broken Packages 
@@ -325,10 +326,6 @@ Packages that can be built within the pkgsrc framework but are not yet necessari
 
 * To search and/or report bugs against packages in pkgsrc, look at [http://www.netbsd.org/support/send-pr.html](http://www.netbsd.org/support/send-pr.html) - use category 'pkg'.
 
-* [http://pkgsrc-wip.sourceforge.net](http://pkgsrc-wip.sourceforge.net), **w**ork **i**n **p**rogress packages not yet in official pkgsrc release
-
-* An [in-depth explanation of pkgsrc](http://www.unixgarden.com/index.php/administration-reseau/netbsd-s01e03-gestion-des-paquets), in French.
-
 * The #pkgsrc IRC channel on Freenode
 
 * The #dragonflybsd IRC channel on EFnet