diff --git a/hgext/largefiles/__init__.py b/hgext/largefiles/__init__.py
--- a/hgext/largefiles/__init__.py
+++ b/hgext/largefiles/__init__.py
@@ -29,7 +29,7 @@ bandwidth, since you don't need to retri
 of large files when you clone or pull.
 
 To start a new repository or add new large binary files, just add
---large to your ``hg add`` command. For example::
+--large to your :hg:`add` command. For example::
 
   $ dd if=/dev/urandom of=randomdata count=2000
   $ hg add --large randomdata
@@ -49,8 +49,8 @@ not previously updated to.
 
 If you already have large files tracked by Mercurial without the
 largefiles extension, you will need to convert your repository in
-order to benefit from largefiles. This is done with the 'hg lfconvert'
-command::
+order to benefit from largefiles. This is done with the
+:hg:`lfconvert` command::
 
   $ hg lfconvert --size 10 oldrepo newrepo
 
@@ -66,7 +66,7 @@ to the minimum size in megabytes to trac
   $ hg add --lfsize 2
 
 The ``largefiles.patterns`` config option allows you to specify a list
-of filename patterns (see ``hg help patterns``) that should always be
+of filename patterns (see :hg:`help patterns`) that should always be
 tracked as largefiles::
 
   [largefiles]