1 files changed, 16 insertions, 16 deletions
diff --git a/sbin/devfs/devfs.8 b/sbin/devfs/devfs.8
index 0953429..80facf7 100644
--- a/sbin/devfs/devfs.8
+++ b/sbin/devfs/devfs.8
@@ -117,7 +117,7 @@ to the mount-point.
 Rules that are
 .Dq applied
 have their conditions checked against all nodes
-in the mount-point, and the actions taken if they match.
+in the mount-point and the actions taken if they match.
 .It Cm rule applyset
 Apply all the rules in the ruleset to the mount-point
 (see above for the definition of
@@ -143,7 +143,7 @@ as the current ruleset for the mount-point.
 .El
 .Ss Rule Specification
 Rules have two parts: the conditions and the actions.
-The conditions determine which DEVFS nodes the rule matches,
+The conditions determine which DEVFS nodes the rule matches
 and the actions determine what should be done when a rule matches a node.
 For example, a rule can be written that sets the GID to
 .Dq Li games
@@ -162,8 +162,8 @@ Matches any node with a major number equal to
 .Ar majdev .
 .It Cm path Ar pattern
 Matches any node with a path that matches
-.Ar pattern .
-The latter is interpreted as a
+.Ar pattern ,
+which is interpreted as a
 .Xr glob 3 Ns -style
 pattern.
 .It Cm type Ar devtype
@@ -189,7 +189,7 @@ or number.
 .It Cm hide
 Hide the node.
 Nodes may later be revived manually with
-.Xr mknod 8 ,
+.Xr mknod 8
 or with the
 .Cm unhide
 action.
@@ -215,13 +215,13 @@ or number.
 Unhide the node.
 .El
 .Sh IMPLEMENTATION NOTES
-Rulesets are created by the kernel at the first reference,
+Rulesets are created by the kernel at the first reference
 and destroyed when the last reference disappears.
 E.g., a ruleset is created when a rule is added to it or when it is set
-as the current ruleset for a mount-point;
-a ruleset is destroyed when the last rule in it is deleted,
+as the current ruleset for a mount-point, and
+a ruleset is destroyed when the last rule in it is deleted
 and no other references to it exist
-(i.e., it is not included by any rules, and it is not the current ruleset
+(i.e., it is not included by any rules and it is not the current ruleset
 for any mount-point).
 .Pp
 Ruleset number 0 is the default ruleset for all new mount-points.
@@ -235,7 +235,7 @@ I.e., a
 .Cm showsets
 will return the same information regardless of the mount-point specified with
 .Fl m .
-The mount-point is only relevant when changing what its current ruleset is,
+The mount-point is only relevant when changing what its current ruleset is
 or when using one of the apply commands.
 .Sh EXAMPLES
 When the system boots,
@@ -278,8 +278,8 @@ Apply all the rules in the current ruleset to all the existing nodes.
 E.g., if the above rule was added after
 .Pa /dev/speaker
 was created,
-this command will cause its file mode to be changed to 666,
-as rule prescribes.
+this command will cause its file mode to be changed to 666
+as prescribed by the rule.
 .Pp
 .Dl devfs rule add path "snp*" mode 660 group snoopers
 .Pp
@@ -288,7 +288,7 @@ as rule prescribes.
 is often necessary to disable the shell's globbing features.)
 For all devices with a path that matches
 .Dq Li snp* ,
-set the file more to 660, and the GID to
+set the file more to 660 and the GID to
 .Dq Li snoopers .
 This permits users in the
 .Dq Li snoopers
@@ -309,14 +309,14 @@ However, it can be applied explicitly, as such:
 This will apply all rules in ruleset number 20 to the DEVFS mount on
 .Pa /my/jail/dev .
 It does not matter that ruleset 20 is not the current ruleset for that
-mount-point; the rules are applied regardless.
+mount-point; the rules are still applied.
 .Pp
 .Dl "devfs rule apply hide"
 .Pp
 Since this rule has no conditions, the action
 .Pq Cm hide
 will be applied to all nodes.
-Since hiding all nodes is not very useful, we can undo like so:
+Since hiding all nodes is not very useful, we can undo it:
 .Pp
 .Dl "devfs rule apply unhide"
 .Pp
@@ -325,7 +325,7 @@ which applies
 to all the nodes,
 causing them to reappear.
 .Pp
-.Dl "cat my_rules | devfs rule -s 10 add -"
+.Dl "devfs rule -s 10 add - < my_rules"
 .Pp
 Add all the rules from the file
 .Pa my_rules