diff --git a/user_guide_src/source/outgoing/localization.rst b/user_guide_src/source/outgoing/localization.rst
index f1ae44282bec..7c44c72ba5e1 100644
--- a/user_guide_src/source/outgoing/localization.rst
+++ b/user_guide_src/source/outgoing/localization.rst
@@ -370,12 +370,12 @@ Detailed information can be found by running the command:
 .. _sync-translations-command:
 
 Synchronization Translation Files via Command
-=============================================
+---------------------------------------------
 
 .. versionadded:: 4.6.0
 
 After working on your translation for the current language for a long time, in some cases you will need to create files for another language.
-The ``spark lang:find`` command can be used, it is not prohibited. But it cannot fully detect absolutely all translations. Especially if the parameters are dynamically set as ``lang('App.status.' . $key, ['payload' => 'John'], 'en')``.
+The ``spark lang:find`` command can be used. But it cannot fully detect absolutely all translations. Especially if the parameters are dynamically set as ``lang('App.status.' . $key, ['payload' => 'John'], 'en')``.
 In this case, the best solution is to copy the finished language files and translate them. This way you can save your unique keys that the command did not find.
 
 All you need to do is execute: