diff --git a/source/developers/concepts/hooks_extension_framework.rst b/source/developers/concepts/hooks_extension_framework.rst
index 95a37fa0f..cbc2b7952 100644
--- a/source/developers/concepts/hooks_extension_framework.rst
+++ b/source/developers/concepts/hooks_extension_framework.rst
@@ -184,9 +184,9 @@ The Hooks Extension Framework is designed to provide a stable and maintainable w
 | **Disadvantages**                                                  | - Can increase complexity in debugging and maintenance because it adds more processing layers.                | - Separation from the separation from the upstream project makes long-term maintenance challenging.                                |
 |                                                                    | - Limited by existing events and filters available in the Open edX ecosystem, although new events and         | - High maintenance burden for upgrades and compatibility.                                                                          |
 |                                                                    |   filters can be proposed and added to the framework.                                                         | - Requires manual integration with the Open edX platform for each new release.                                                     |
-|                                                                    | - Might increase complexity in plugins for highly customized features.                                        | - Requires deep understanding of the platform to modify it.                                                                        |
-|                                                                    | - Although it is not recommended to do so, a plugin developer might introduce an edx-platform dependency,     | - Not being able to be reused by the community.                                                                                    |
-|                                                                    |   mainly when using filters, when there is no alternative for getting certain types of data.                  | - Difficult to test in isolation due to highly coupled implementations.                                                            |
+|                                                                    | - Might increase complexity in plugins for highly customized features.                                        | - Not being able to be reused by the community.                                                                                    |
+|                                                                    | - Although it is not recommended to do so, a plugin developer might introduce an edx-platform dependency,     | - Difficult to test in isolation due to highly coupled implementations.                                                            |
+|                                                                    |   mainly when using filters, when there is no alternative for getting certain types of data.                  |                                                                                                                                    |
 +--------------------------------------------------------------------+---------------------------------------------------------------------------------------------------------------+------------------------------------------------------------------------------------------------------------------------------------+
 | **Community Compatibility**                                        | High, as the community encourages reusable implementations and the contribution of new extension points.      | Low, as changes in forks are usually extremely customized not designed for others to reuse. Also,                                  |
 |                                                                    |                                                                                                               | community discoverability is low when changes are kept in a fork, making it harder to share and collaborate.                       |
@@ -197,7 +197,7 @@ The Hooks Extension Framework is designed to provide a stable and maintainable w
 | **Upgrade Compatibility**                                          | High, due to backward compatibility policies.                                                                 | Low, as forks must manually integrate their changes with the Open edX platform for each new release.                               |
 +--------------------------------------------------------------------+---------------------------------------------------------------------------------------------------------------+------------------------------------------------------------------------------------------------------------------------------------+
 
-When implementing a new feature, look into how the Hooks Extension Framework can help you extend the platform before considering forking the Open edX platform. You should consider the advantages and disadvantages of each approach to determine the best fit for your use case and long-term goals. 
+When implementing a new feature, look into how the Hooks Extension Framework can help you extend the platform before considering forking the Open edX platform. You should consider the advantages and disadvantages of each approach to determine the best fit for your use case and long-term goals.
 
 .. note:: If you think your feature should be part of the core instead of an extension, consider making a `Product Proposal`_.