Ticket #694: fhs.pod.diff

docs/dev/fhs.pod

@@ +1 @@
+# Copyright (C) 2001-2007, Parrot Foundation.
+# $Id$
+
 =pod
 
 =head1 Title
@@ -2 +5 @@
 
-FHS - Filesystem Hieararchy Standard and Parrot
+FHS - Filesystem Hierarchy Standard and Parrot
 
@@ -53 +56 @@
 
 This is the primary directory of executable commands on the system. All
 executables that are intended to be called directly by the user (i.e.
-parrot, pdump, disassemble, parrot-debugger, pbc_info,  pbg_merge, ...)
+parrot, parrot_debugger, pbc_disassemble, pbc_dump, pbc_info, pbg_merge, ...)
 should go here. The current version number should be appended to the
 binaries itself and a symlink needs to be created that points from the
 binary with version number to the normal name of the file without a
@@ -79 +82 @@
 This is libparrot$(SOEXT).$(SOVERSION) if the parrot binary was linked
 dynamically. Otherwise nothing.
 
-Also Parrot usees a single subdirectory called I</usr/lib/parrot> to
+Also Parrot uses a single subdirectory called I</usr/lib/parrot> to
 store all architecture-dependent data exclusively used by parrot. These
 files are grouped by the parrot version they belong to. So we'll have
 I</usr/lib/parrot/0.4.0>, I</usr/lib/parrot/0.4.1>, etc.
@@ -97 +100 @@
 
 The I</usr/share> hierarchy is for all read-only architecture
 independent data files. Parrot stores those files in
-I</usr/share/parrot/$(VERSION)>. For example all .imc, .pasm and  .imc
+I</usr/share/parrot/$(VERSION)>. For example all .pasm and .pir
 files should go there as well as data files for libraries like images
 and such.
 
@@ -154 +157 @@
 
 This is also documentation for I</usr/share/doc>.
 
-=item /usr/parrot-config.imc
+=item /usr/parrot-config.pir
 
 This is a command which can be called from the user. It should be in
-I</usr/bin>, maybe without the .imc suffix.
+I</usr/bin>, maybe without the .pir suffix.
 
 =back