From f3b5ad46c8d6e1b39200490702d6c7e2c7240b06 Mon Sep 17 00:00:00 2001 From: =?UTF-8?q?Michal=20=C4=8Ciha=C5=99?= Date: Tue, 19 Dec 2023 09:33:27 +0100 Subject: [PATCH] docs: apply feedback from #9275 --- docs/devel/integration.rst | 8 ++++---- 1 file changed, 4 insertions(+), 4 deletions(-) diff --git a/docs/devel/integration.rst b/docs/devel/integration.rst index 8693fb71a028..852f22d304fd 100644 --- a/docs/devel/integration.rst +++ b/docs/devel/integration.rst @@ -65,13 +65,13 @@ translations to match your code base. Adding new strings ++++++++++++++++++ -In case your translation files are stored in a VCS together with the code, +If your translation files are stored in a remote VCS together with the code, you most likely have an existing workflow for developers to introduce new strings. Any way of adding strings will be picked up, but consider using :ref:`source-quality-gateway` to avoid introducing errors. -When the translation files are separate from the code, there are following ways to introduce -new strings into Weblate. +When translation files are separated from the code, the following ways can +introduce new strings into Weblate. * Manually, using :guilabel:`Add new translation string` from :guilabel:`Tools` menu in the source language. @@ -82,7 +82,7 @@ new strings into Weblate. .. note:: - Availability of adding strings in Weblate depends on :ref:`component-manage_units`. + The ability to add strings in Weblate requires :ref:`component-manage_units`. .. _updating-target-files: