diff --git a/docs/source/dev/hwobj_signals.md b/docs/source/dev/hwobj_signals.md
index 5c5ea758a9..fab2577c8e 100644
--- a/docs/source/dev/hwobj_signals.md
+++ b/docs/source/dev/hwobj_signals.md
@@ -38,7 +38,7 @@ From the {py:class}`HardwareObjectMixin` class (removing extra lines for brevity
         dispatcher.send(signal, self, *args)
 ```
 
-So, in a custom hardware object, since it inherits from {py:class}`HardwareObject`, one only needs to call: 
+So, in a custom hardware object, since it inherits from {py:class}`HardwareObject`, one only needs to call:
 ```
 self.emit('my_signal', new_value)
 ```
@@ -136,7 +136,7 @@ class HO1(HardwareObject):
         gevent.spawn(self.update_value)
 
     def stop(self):
-        self.run = False	
+        self.run = False
 ```
 
 and a data consumer:
@@ -175,11 +175,11 @@ In [1]: from mxcubecore import HardwareRepository as hwr
    ...: ho2 = hwrTest.get_hardware_object("/ho2")
 2024-03-18 12:20:18,434 |INFO   | Hardware repository: ['/Users/mikegu/Documents/MXCUBE/mxcubecore_upstream/mxcubecore/configuration/mockup/test']
 +======================================================================================+
-| role             | Class      | file                   | Time (ms)| Comment                   
+| role             | Class      | file                   | Time (ms)| Comment
 +======================================================================================+
-| beamline         | Beamline   | beamline_config.yml    | 9        | Start loading contents:   
-| mock_procedure   | None       | procedure-mockup.yml   | 0        | File not found            
-| beamline         | Beamline   | beamline_config.yml    | 9        | Done loading contents     
+| beamline         | Beamline   | beamline_config.yml    | 9        | Start loading contents:
+| mock_procedure   | None       | procedure-mockup.yml   | 0        | File not found
+| beamline         | Beamline   | beamline_config.yml    | 9        | Done loading contents
 +======================================================================================+
 
 In [2]: ho1.start()
@@ -207,7 +207,7 @@ As you can see, the second hardware object receives and processes first one's si
 
 ## General signals List
 
-The following tables list the generic signals as well as the signals from some of the most important hardware objects. 
+The following tables list the generic signals as well as the signals from some of the most important hardware objects.
 >Additional signal could be emitted by other hardware objects. For example, "energyScanFinished" by the energy scan object, and similars. For the shake of keeping this document digestable not all the signals are listed.
 
 
@@ -336,4 +336,3 @@ motor_positions = {
 | centringAccepted |    | "centringAccepted", (bool: accepted, dict:centring_status) | |
 | centringSnapshots |    | "centringSnapshots", boolean | |
 | progressMessage |    | "progressMessage", msg | |
-
diff --git a/mxcubecore/HardwareObjects/abstract/AbstractBeam.py b/mxcubecore/HardwareObjects/abstract/AbstractBeam.py
index f17532445e..db8fd51893 100644
--- a/mxcubecore/HardwareObjects/abstract/AbstractBeam.py
+++ b/mxcubecore/HardwareObjects/abstract/AbstractBeam.py
@@ -19,7 +19,6 @@
 #  along with MXCuBE. If not, see <http://www.gnu.org/licenses/>.
 
 
-
 __copyright__ = """ Copyright © 2016 - 2022 by MXCuBE Collaboration """
 __license__ = "LGPLv3+"