1 files changed, 17 insertions, 17 deletions
diff --git a/usr/src/man/man7/smf_bootstrap.7 b/usr/src/man/man7/smf_bootstrap.7
index 57af969a62..fa44f1ef9d 100644
--- a/usr/src/man/man7/smf_bootstrap.7
+++ b/usr/src/man/man7/smf_bootstrap.7
@@ -17,7 +17,7 @@ service profiles.
 .SS "Manifest Loading at Boot"
 .sp
 .LP
-The \fBsvc:/system/manifest-import:default\fR service uses \fBsvccfg\fR(1M) to
+The \fBsvc:/system/manifest-import:default\fR service uses \fBsvccfg\fR(8) to
 import certain manifest files from the \fB/var/svc/manifest\fR directory tree
 into the service configuration repository. The service imports files that it
 has not imported previously and those files which have changed since the last
@@ -25,46 +25,46 @@ time they were imported by the service. When a manifest is imported by the
 service, a hash of the file that includes its contents is recorded in a
 property group of the \fBsvc:/smf/manifest\fR service. The
 \fBmanifest-import\fR service uses the hash to determine whether the file has
-changed. See \fBsvccfg\fR(1M) for information on the \fBsvccfg import\fR
+changed. See \fBsvccfg\fR(8) for information on the \fBsvccfg import\fR
 behavior for services that already exist in the repository.
 .SS "Manifest Handling During Packaging Operations"
 .sp
 .LP
 Service manifests within packages should be identified with the class
 \fBmanifest\fR. Class action scripts that install and remove service manifests
-are included in the packaging subsystem. When \fBpkgadd\fR(1M) is invoked, the
+are included in the packaging subsystem. When \fBpkgadd\fR(8) is invoked, the
 service manifest is imported.
 .sp
 .LP
-When \fBpkgrm\fR(1M) is invoked, instances in the manifest that are disabled
+When \fBpkgrm\fR(8) is invoked, instances in the manifest that are disabled
 are deleted. Instances in the manifest that are online or degraded are disabled
 first and then deleted. Any services in the manifest with no remaining
 instances are also deleted.
 .sp
 .LP
-If the \fB-R\fR option is supplied to \fBpkgadd\fR(1M) or \fBpkgrm\fR(1M), the
+If the \fB-R\fR option is supplied to \fBpkgadd\fR(8) or \fBpkgrm\fR(8), the
 actions described in this section will be done when the system is next rebooted
 with that alternate root path.
 .SS "Stability Declarations"
 .sp
 .LP
 Each service group and each property group delivered in a manifest should
-declare a stability level based on \fBattributes\fR(5) definitions. With
+declare a stability level based on \fBattributes\fR(7) definitions. With
 knowledge of the stability level, an application developer can determine the
 likelihood that feature development based on the existence or components of a
 service or object is likely to remain functional across a release boundary.
 .sp
 .LP
-In an \fBsmf\fR(5) context, the stability value also identifies the expected
+In an \fBsmf\fR(7) context, the stability value also identifies the expected
 scope of the changes to properties within the property group across a release
 boundary for the service, which can include patches for that service. The
 following two sections discuss this in more detail.
 .SS "Property Overrides"
 .sp
 .LP
-The \fBservice_bundle\fR(4) document type definition includes an override
+The \fBservice_bundle\fR(5) document type definition includes an override
 attribute that is applicable to each property in a service manifest. If set to
-\fBtrue\fR, the attribute instructs \fBsvccfg\fR(1M) and other manifest import
+\fBtrue\fR, the attribute instructs \fBsvccfg\fR(8) and other manifest import
 tools to replace the current value of a property in the repository with the one
 from the manifest. If the override attribute is absent or present but set to
 \fBfalse\fR, the current value in the repository is preserved.
@@ -79,9 +79,9 @@ interface presented by the service.
 .SS "Property Group Deletion"
 .sp
 .LP
-The \fBservice_bundle\fR(4) document type definition includes a delete
+The \fBservice_bundle\fR(5) document type definition includes a delete
 attribute, applicable to each property group in a service manifest. If set to
-\fBtrue\fR, the delete attribute instructs \fBsvccfg\fR(1M) and other manifest
+\fBtrue\fR, the delete attribute instructs \fBsvccfg\fR(8) and other manifest
 import tools to delete this property group from the repository. If the delete
 attribute is absent or present but set to \fBfalse\fR, the property group in
 the repository is preserved.
@@ -93,7 +93,7 @@ declared as Unstable can be deleted across any release boundary.
 .sp
 .LP
 The first time the existence of each of the three service profiles listed below
-is detected, \fBsvc.startd\fR(1M) automatically applies the profile.
+is detected, \fBsvc.startd\fR(8) automatically applies the profile.
 .sp
 .in +2
 .nf
@@ -111,14 +111,14 @@ The \fBsvc:/smf/manifest\fR service is used in a similar fashion.
 Additional service profiles that characterize the activation of various groups
 of service instances might be present in \fB/var/svc/profile\fR. None of the
 \fB/var/svc/profile\fR profiles are automatically applied to the repository. A
-profile can be manually applied or re-applied using \fBsvccfg\fR(1M).
+profile can be manually applied or re-applied using \fBsvccfg\fR(8).
 .SH SEE ALSO
 .sp
 .LP
-\fBpkgadd\fR(1M), \fBpkgrm\fR(1M), \fBsvcadm\fR(1M), \fBsvccfg\fR(1M),
-\fBsvc.startd\fR(1M), \fBlibscf\fR(3LIB), \fBservice_bundle\fR(4),
-\fBattributes\fR(5), \fBsmf\fR(5), \fBsmf_security\fR(5)
+\fBpkgadd\fR(8), \fBpkgrm\fR(8), \fBsvcadm\fR(8), \fBsvccfg\fR(8),
+\fBsvc.startd\fR(8), \fBlibscf\fR(3LIB), \fBservice_bundle\fR(5),
+\fBattributes\fR(7), \fBsmf\fR(7), \fBsmf_security\fR(7)
 .SH NOTES
 .sp
 .LP
-The present version of \fBsmf\fR(5) does not support multiple repositories.
+The present version of \fBsmf\fR(7) does not support multiple repositories.