From 2ace7f0b6f45ec4cc030cf1b7e7ecbc7109eac18 Mon Sep 17 00:00:00 2001 From: Bence Magyar Date: Thu, 24 Aug 2023 21:19:12 +0100 Subject: [PATCH] small rephrasing --- controller_manager/doc/controller_chaining.rst | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) diff --git a/controller_manager/doc/controller_chaining.rst b/controller_manager/doc/controller_chaining.rst index 32d9a95b35..d79e730d3f 100644 --- a/controller_manager/doc/controller_chaining.rst +++ b/controller_manager/doc/controller_chaining.rst @@ -67,10 +67,10 @@ Controller manager maintains "claimed" status of interface in a vector (the same Activation and Deactivation Chained Controllers ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ -The chained controller must be activated and deactivated together or in the proper order. +Chained controllers must be activated and deactivated together or in the proper order. This means you must first activate all following controllers to have the preceding one activated. For the deactivation there is the inverse rule - all preceding controllers have to be deactivated before the following controller is deactivated. -If you imagine a chain of controllers, you can not add a chain link or break the chain in the middle. +One can also think of it as an actual chain, you can not add a chain link or break the chain in the middle. Debugging outputs