svn commit: r269439 - head/share/man/man9

[Hans Petter Selasky]

Author: hselasky
Date: Sat Aug  2 18:37:08 2014
New Revision: 269439
URL: http://svnweb.freebsd.org/changeset/base/269439

Log:
  - Spelling corrections
  
  Suggested by:	Garrett Cooper <yaneurabeya at gmail.com>
  PR:		192101

Modified:
  head/share/man/man9/sysctl.9

Modified: head/share/man/man9/sysctl.9
==============================================================================
--- head/share/man/man9/sysctl.9	Sat Aug  2 17:58:20 2014	(r269438)
+++ head/share/man/man9/sysctl.9	Sat Aug  2 18:37:08 2014	(r269439)
@@ -243,22 +243,22 @@ See
 for how to create a new sysctl context.
 Programmers are strongly advised to use contexts to organize the
 dynamic OIDs which they create because when a context is destroyed all
-belonging sysctls are destroyed aswell.
+belonging sysctls are destroyed as well.
 This makes the sysctl cleanup code much simpler.
-Else deletion of all created OIDs is required at module unload typically.
+Else deletion of all created OIDs is required at module unload.
 .It Fa parent
 A pointer to a
 .Li struct sysctl_oid_list ,
 which is the head of the parent's list of children.
-This pointer is retrieved by using the
+This pointer is retrieved using the
 .Fn SYSCTL_STATIC_CHILDREN
 macro for static sysctls and the
 .Fn SYSCTL_CHILDREN
 macro for dynamic sysctls.
-To get the parent of an OID the
+The
 .Fn SYSCTL_PARENT
-macro shall be used.
-If there is no parent this macro returns NULL.
+macro can be used to get the parent of an OID.
+The macro returns NULL if there is no parent.
 .It Fa number
 The OID number that will be assigned to this OID.
 In almost all cases this should be set to