Fix clerical errors in 2 guides
Node Management index: change BCM to BMC Fault Management guide: remove “ing” from title of 2 topics Change-Id: I33b4c29e2ca92e842f585f4bb641780b52769206 Signed-off-by: MCamp859 <maryx.camp@intel.com>
This commit is contained in:
parent
8eb91b7190
commit
ebdf63ec68
@ -2,9 +2,9 @@
|
||||
.. sla1552680666298
|
||||
.. _suppressing-and-unsuppressing-events:
|
||||
|
||||
=================================
|
||||
Suppress and Unsuppressing Events
|
||||
=================================
|
||||
==============================
|
||||
Suppress and Unsuppress Events
|
||||
==============================
|
||||
|
||||
You can set events to a suppressed state and toggle them back to unsuppressed.
|
||||
|
||||
|
@ -2,9 +2,9 @@
|
||||
.. maj1552680619436
|
||||
.. _unsuppressing-an-alarm-using-the-cli:
|
||||
|
||||
====================================
|
||||
Unsuppressing an Alarm Using the CLI
|
||||
====================================
|
||||
=================================
|
||||
Unsuppress an Alarm Using the CLI
|
||||
=================================
|
||||
|
||||
If you need to reactivate a suppressed alarm, you can do so using the CLI.
|
||||
|
||||
|
@ -303,10 +303,10 @@ Run the node feature discovery helm chart
|
||||
starlingx-kubernetes/running-the-node-feature-discovery-helm-chart
|
||||
|
||||
*************
|
||||
Provision BCM
|
||||
Provision BMC
|
||||
*************
|
||||
|
||||
Provision BCM using Horizon
|
||||
Provision BMC using Horizon
|
||||
***************************
|
||||
|
||||
.. toctree::
|
||||
@ -315,7 +315,7 @@ Provision BCM using Horizon
|
||||
starlingx-kubernetes/provisioning_bmc/provisioning-board-management-control-from-horizon
|
||||
starlingx-kubernetes/provisioning_bmc/deprovisioning-board-management-control-from-horizon
|
||||
|
||||
Provision BCM using the CLI
|
||||
Provision BMC using the CLI
|
||||
***************************
|
||||
|
||||
.. toctree::
|
||||
|
Loading…
x
Reference in New Issue
Block a user