From aaa7cea4ca0c2a19f72ad0ed5dfdeba20daf8441 Mon Sep 17 00:00:00 2001 From: Pierre Riteau Date: Tue, 18 Nov 2025 15:02:03 +0100 Subject: [PATCH] docs: Fix typos and a wrong URL Change-Id: I497577fc4371eb66db023ff1c4fab39564398855 Signed-off-by: Pierre Riteau --- doc/source/admin/inspection/index.rst | 11 +++++------ 1 file changed, 5 insertions(+), 6 deletions(-) diff --git a/doc/source/admin/inspection/index.rst b/doc/source/admin/inspection/index.rst index 18147487b4..1441cefd74 100644 --- a/doc/source/admin/inspection/index.rst +++ b/doc/source/admin/inspection/index.rst @@ -31,9 +31,9 @@ ironic-inspector_ service. pxe_filter migration -Inspection rules have now been migrate into Ironic as of 2025.1 "Epoxy" -release. This does not include support for reapplying inspection on -already stored data, nor does it support the ``"scope"`` field. +Inspection rules have now been migrated into Ironic as of the 2025.1 "Epoxy" +release. This does not include support for reapplying inspection on already +stored data, nor does it support the ``"scope"`` field. The scope field allowed a rule to be applied only to specific nodes with matching scope value rather than all nodes where conditions are met. @@ -53,11 +53,10 @@ Ironic provides an API to manage such rules. There are also built-in rules which are pre-saved and loaded from a YAML file and cannot be CRUD through the API. -Available conditions and actions are defined by an extendedable set of -plugins. +Available conditions and actions are defined by an extendable set of plugins. Refer to the -`Ironic API reference for inspection rules `_ +`Ironic API reference for inspection rules `_ for information on how to CRUD inspection rules. Actions & Conditions