X-Git-Url: http://wien.tomnetworks.com/gitweb/?a=blobdiff_plain;f=man%2Flc.1;h=795b855fb1cdd447727ce5ae97087105fb256660;hb=HEAD;hp=9e5f307ee5c26cadf6f35cdca2aa0fcd24dd0631;hpb=8ec2c4c64ae7f5a1595709aae717d2dd545b7dc3;p=mono.git

diff --git a/man/lc.1 b/man/lc.1
index 9e5f307ee5c..795b855fb1c 100644
--- a/man/lc.1
+++ b/man/lc.1
@@ -9,7 +9,7 @@
 .if t .sp .5v
 .if n .sp
 ..
-.TH lc "Mono 2.6"
+.TH Mono "lc"
 .SH NAME
 lc \- Mono License Compiler
 .SH SYNOPSIS
@@ -24,7 +24,7 @@ resource at runtime to make sure the developer was licensed to use this
 control. The most common way of making sure the component was properly
 licensed is by using license resources. At compile time the developer
 uses the \fIlc\fP tool to convert a licenses.licx file to a 
-programname.exe.resources file and embed that as a managed resource 
+programname.exe.licenses file and embed that as a managed resource
 during compilation.
 .SH RUNTIME OPTIONS
 The following options are available:
@@ -52,7 +52,7 @@ Gives more verbose output about the license compiling process.
 \fB--help\fR, \fB-h\fR
 Displays usage instructions.
 .TP
-\fB--output=path\fR, \fB-o path\fR
+\fB--outdir=path\fR, \fB-o path\fR
 Target path file the licenses resource. By default the license
 compiler emits the resource in the current directory. The filename
 will always match the target assembly passed to --target with .licenses 
@@ -78,7 +78,7 @@ version and publickeytoken.
 
 .SH MAILING LISTS
 Mailing lists are listed at the
-http://www.mono-project.com/Mailing_Lists
+http://www.mono-project.com/community/help/mailing-lists/
 .SH WEB SITE
 http://www.mono-project.com
 .SH SEE ALSO