Apply suggestions from code review

Co-authored-by: Simon André <smn.andre@gmail.com>

Author: maelanleborgne

src/Translator/doc/index.rst

@@ -71,10 +71,10 @@ For a better developer experience, TypeScript types definitions are also generat
 Then, you will be able to import those JavaScript translations in your assets.
 Don't worry about your final bundle size, only the translations you use will be included in your final bundle, thanks to the `tree shaking <https://webpack.js.org/guides/tree-shaking/>`_.
 
-Configuring the dumped translations
+Restrict the translation domains
 ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
 
-By default, all your translations will be dumped as JavaScript. You can restrict the dumped translations by either
+By default, all your translations will be exported. You can restrict the dumped messages by either
 including or excluding translation domains in your ``config/packages/ux_translator.yaml`` file:
 
 .. code-block:: yaml

src/Translator/src/DependencyInjection/UxTranslatorExtension.php

@@ -38,10 +38,10 @@ public function load(array $configs, ContainerBuilder $container)
         $dumperDefinition = $container->getDefinition('ux.translator.translations_dumper');
         $dumperDefinition->setArgument(0, $config['dump_directory']);
 
-        if (0 !== \count($config['excluded_domains'])) {
+        if ($config['excluded_domains']) {
             $dumperDefinition->addMethodCall('setExcludedDomains', [$config['excluded_domains']]);
         }
-        if (0 !== \count($config['included_domains'])) {
+        if ($config['included_domains']) {
             $dumperDefinition->addMethodCall('setIncludedDomains', [$config['included_domains']]);
         }
     }