6 files changed, 14 insertions, 14 deletions
diff --git a/sys/miscfs/devfs/README b/sys/miscfs/devfs/README
index 09c74f2..e99aa8d 100644
--- a/sys/miscfs/devfs/README
+++ b/sys/miscfs/devfs/README
@@ -93,7 +93,7 @@ node, and deletes them, no matter where they've been moved to.
 (active vnodes are redirected to point to the deadfs).
 
 If a directory has been moved, and a new backing node is inserted
-into it's own back node, the new front node will appear in that front
+into its own back node, the new front node will appear in that front
 directory, even though it's been moved, because the directory that
 gets the front node is found via the links and not by name.
 
diff --git a/sys/miscfs/devfs/devfs_tree.c b/sys/miscfs/devfs/devfs_tree.c
index 20d46f1..c7c561e 100644
--- a/sys/miscfs/devfs/devfs_tree.c
+++ b/sys/miscfs/devfs/devfs_tree.c
@@ -24,7 +24,7 @@
  * OUT OF THE USE OF THIS SOFTWARE, EVEN IF ADVISED OF THE POSSIBILITY OF
  * SUCH DAMAGE.
  * 
- *	$Id: devfs_tree.c,v 1.49 1998/01/02 07:31:06 julian Exp $
+ *	$Id: devfs_tree.c,v 1.50 1998/03/26 20:52:05 phk Exp $
  */
 
 #include "opt_devfs.h"
@@ -314,7 +314,7 @@ dev_add_name(char *name, dn_p dirnode, devnm_p back, dn_p dnp,
 	if(dnp->type == DEV_DIR) {
 		dnp->by.Dir.myname = devnmp;
 		/*
-		 * If we are unlinking from an old dir, decrement it's links
+		 * If we are unlinking from an old dir, decrement its links
 		 * as we point our '..' elsewhere
 		 * Note: it's up to the calling code to remove the 
 		 * us from the original directory's list
@@ -472,7 +472,7 @@ dev_add_node(int entrytype, union typeinfo *by, dn_p proto,
 		 * Symlinks should only ever be created by the user,
 		 * so they are not on the back plane and should not be 
 		 * propogated forward.. a bit like directories in that way..
-		 * A symlink only exists on one plane and has it's own
+		 * A symlink only exists on one plane and has its own
 		 * node.. therefore we might be on any random plane.
 		 */
 		dnp->by.Slnk.name = malloc(by->Slnk.namelen+1,
@@ -813,7 +813,7 @@ dev_free_name(devnm_p devnmp)
 	}
 
 	/***************************************************************\
-	* If the front node has it's own devnode structure,		*
+	* If the front node has its own devnode structure,		*
 	* then free it.							*
 	\***************************************************************/
 	free(devnmp,M_DEVFSNAME);
diff --git a/sys/miscfs/devfs/devfs_vfsops.c b/sys/miscfs/devfs/devfs_vfsops.c
index 199ed5e..442dc1b 100644
--- a/sys/miscfs/devfs/devfs_vfsops.c
+++ b/sys/miscfs/devfs/devfs_vfsops.c
@@ -23,7 +23,7 @@
  * OUT OF THE USE OF THIS SOFTWARE, EVEN IF ADVISED OF THE POSSIBILITY OF
  * SUCH DAMAGE.
  * 
- *	$Id: devfs_vfsops.c,v 1.26 1998/01/02 07:31:06 julian Exp $
+ *	$Id: devfs_vfsops.c,v 1.27 1998/03/01 22:46:08 msmith Exp $
  *
  */
 
@@ -80,7 +80,7 @@ devfs_init(struct vfsconf *vfsp)
  *  ndp  - namei data pointer
  *  p    - proc pointer
  * devfs is special in that it doesn't require any device to be mounted..
- * It makes up it's data as it goes along.
+ * It makes up its data as it goes along.
  * it must be mounted during single user.. until it is, only std{in/out/err}
  * and the root filesystem are available.
  */
diff --git a/sys/miscfs/nullfs/null_vnops.c b/sys/miscfs/nullfs/null_vnops.c
index 9575487..877fc37 100644
--- a/sys/miscfs/nullfs/null_vnops.c
+++ b/sys/miscfs/nullfs/null_vnops.c
@@ -37,11 +37,11 @@
  *
  * Ancestors:
  *	@(#)lofs_vnops.c	1.2 (Berkeley) 6/18/92
- *	$Id: null_vnops.c,v 1.25 1997/10/21 21:01:34 roberto Exp $
+ *	$Id: null_vnops.c,v 1.26 1998/01/31 07:23:13 eivind Exp $
  *	...and...
  *	@(#)null_vnodeops.c 1.20 92/07/07 UCLA Ficus project
  *
- * $Id: null_vnops.c,v 1.25 1997/10/21 21:01:34 roberto Exp $
+ * $Id: null_vnops.c,v 1.26 1998/01/31 07:23:13 eivind Exp $
  */
 
 /*
@@ -53,7 +53,7 @@
  * name space under a new name.  In this respect, it is
  * similar to the loopback file system.  It differs from
  * the loopback fs in two respects:  it is implemented using
- * a stackable layers techniques, and it's "null-node"s stack above
+ * a stackable layers techniques, and its "null-node"s stack above
  * all lower-layer vnodes, not just over directory vnodes.
  *
  * The null layer has two purposes.  First, it serves as a demonstration
diff --git a/sys/miscfs/procfs/procfs_mem.c b/sys/miscfs/procfs/procfs_mem.c
index 5625678..5184f47 100644
--- a/sys/miscfs/procfs/procfs_mem.c
+++ b/sys/miscfs/procfs/procfs_mem.c
@@ -37,7 +37,7 @@
  *
  *	@(#)procfs_mem.c	8.5 (Berkeley) 6/15/94
  *
- *	$Id: procfs_mem.c,v 1.29 1998/02/04 22:32:49 eivind Exp $
+ *	$Id: procfs_mem.c,v 1.30 1998/02/06 12:13:41 eivind Exp $
  */
 
 /*
@@ -299,7 +299,7 @@ procfs_domem(curp, p, pfs, uio)
 
 /*
  * Given process (p), find the vnode from which
- * it's text segment is being executed.
+ * its text segment is being executed.
  *
  * It would be nice to grab this information from
  * the VM system, however, there is no sure-fire
diff --git a/sys/miscfs/union/union_vfsops.c b/sys/miscfs/union/union_vfsops.c
index 156108d..2f90d05 100644
--- a/sys/miscfs/union/union_vfsops.c
+++ b/sys/miscfs/union/union_vfsops.c
@@ -35,7 +35,7 @@
  * SUCH DAMAGE.
  *
  *	@(#)union_vfsops.c	8.20 (Berkeley) 5/20/95
- * $Id: union_vfsops.c,v 1.26 1998/02/10 08:04:31 kato Exp $
+ * $Id: union_vfsops.c,v 1.27 1998/03/01 22:46:25 msmith Exp $
  */
 
 /*
@@ -237,7 +237,7 @@ union_mount(mp, path, data, ndp, p)
 	/*
 	 * Copy in the upper layer's RDONLY flag.  This is for the benefit
 	 * of lookup() which explicitly checks the flag, rather than asking
-	 * the filesystem for it's own opinion.  This means, that an update
+	 * the filesystem for its own opinion.  This means, that an update
 	 * mount of the underlying filesystem to go from rdonly to rdwr
 	 * will leave the unioned view as read-only.
 	 */