Add explanation on using configs with serge import

Igor Afanasyev · Igor Afanasyev · commit 35b579476e1d · 2016-05-22T12:20:52.000-07:00
diff --git a/doc/html/serge-import.html b/doc/html/serge-import.html
@@ -34,6 +34,8 @@ <h1 id="DESCRIPTION">DESCRIPTION</h1>
 
 <p>This is useful to initially import pre-existing translations before setting up an automated localization flow.</p>
 
+<p>Note that for import to work, you don&#39;t need to create a separate Serge configuration file or a job: you need to setup Serge jobs for the primary workflow (localization), in each job specifying the path to output localized files using <code>output_file_path</code> parameter. Then make sure that the pre-existing localized files are located and named in accordance with that parameter, and <b>serge-import</b> will know where to find these files for importing.</p>
+
 <h1 id="OPTIONS">OPTIONS</h1>
 
 <dl>
@@ -53,7 +55,7 @@ <h1 id="OPTIONS">OPTIONS</h1>
 <dt><b>--disambiguate-keys</b></dt>
 <dd>
 
-<p>If duplicate keys are found, don&#39;t exit but disambiguate them in the order of their presence. Use with care only when you are sure that the ordering and the number of ambigous keys in all files (both original and localized) is the same, otherwise you might end up importing wrong translations for wrong keys.</p>
+<p>If duplicate keys are found, don&#39;t exit but disambiguate them in the order of their presence. Use with care only when you are sure that the ordering and the number of ambiguous keys in all files (both original and localized) is the same, otherwise you might end up importing wrong translations for wrong keys.</p>
 
 </dd>
 <dt><b>--no-report</b></dt>
diff --git a/doc/pod/serge-import.pod b/doc/pod/serge-import.pod
@@ -20,6 +20,13 @@ and tries to import translations back into the database.
 This is useful to initially import pre-existing translations before setting up an
 automated localization flow.
 
+Note that for import to work, you don't need to create a separate Serge
+configuration file or a job: you need to setup Serge jobs for the primary
+workflow (localization), in each job specifying the path to output localized
+files using C<< output_file_path >> parameter. Then make sure that the pre-existing
+localized files are located and named in accordance with that parameter,
+and B<serge-import> will know where to find these files for importing.
+
 =head1 OPTIONS
 
 =over 8
@@ -36,7 +43,7 @@ An optional comma-separated list of target languages
 
 If duplicate keys are found, don't exit but disambiguate them in
 the order of their presence. Use with care only when you are sure that
-the ordering and the number of ambigous keys in all files (both original
+the ordering and the number of ambiguous keys in all files (both original
 and localized) is the same, otherwise you might end up importing
 wrong translations for wrong keys.
 
