diff --git a/tm/03.userGuide/01.send.md b/tm/03.userGuide/01.send.md index 30c8b31..79796c2 100644 --- a/tm/03.userGuide/01.send.md +++ b/tm/03.userGuide/01.send.md @@ -37,8 +37,8 @@ Depending on the translation connectors you have installed you might see differe Your translation provider may give you options to choose from at this point. Select what you need and continue. ## Completed -Now you will see the Completed screen. +Now you will see the completed screen. ![Completed](completed.png) -From this point you can go on to view your translation job. +Here, you can click on *View Job* to view your translation job. diff --git a/tm/03.userGuide/03.approve.md b/tm/03.userGuide/03.approve.md index 3aec461..c4a0266 100644 --- a/tm/03.userGuide/03.approve.md +++ b/tm/03.userGuide/03.approve.md @@ -14,13 +14,13 @@ There are three buttons at the bottom of the screen when viewing a recieved tran - Archive - - Archives the translation job, **but doesn't save the content to Umbraco.** + - Archives the translation job, **but does not save the content to Umbraco.** - Reset - Resets the job back to submitted. - > This is useful if you require the [Translation Connector](../reference/fundementals/connector) to reprocess the job. + > This is useful if you require a [Translation Connector](../reference/fundementals/connector) to reprocess the job. - Approve - Opens the Aprrove Translations pop-up. diff --git a/tm/03.userGuide/04.create.md b/tm/03.userGuide/04.create.md index 5c8129c..c304688 100644 --- a/tm/03.userGuide/04.create.md +++ b/tm/03.userGuide/04.create.md @@ -52,7 +52,7 @@ Symbol | Use When selected the connector will be used for all content translated with this [Translation Set](../reference/fundementals/set). - If this option isn't selected the editor will be able to choose a connector when sending content for translation. + If this option isn't selected, the editor will be able to choose a connector when sending content for translation. ## Set Flags ![Set flags options](actionsbox.png) @@ -63,11 +63,11 @@ Symbol | Use - Create and Send - Allows your editors to create translation jobs in one step and leaves the [Create Job](send) option on when sending. When this option is off jobs will go via the Pending Queue. + Allows your editors to create translation jobs in one step and leaves the [Create Job](send) option on when sending. When this option is off, jobs will go via the Pending Queue. -- Always create a job +- Always Create a Job - Creates a job every time by default, instead of letting the editor decide. + Creates a job every time, by default, instead of letting the editor decide. - Hide "Include Children" Option @@ -79,7 +79,7 @@ Symbol | Use - Automatic Approval - When this button is selected, a job coming back via a Translation connector will be automatically approved (& published) onto your website without you having to review and approve the content. This button is off by default. + A job coming back via a Translation connector will be automatically approved (& published) onto your website without you having to review and approve the content. This option is off by default. - Replace node name from source diff --git a/tm/03.userGuide/05.backgroundchecks.md b/tm/03.userGuide/05.backgroundchecks.md index 50e0f20..47d6b60 100644 --- a/tm/03.userGuide/05.backgroundchecks.md +++ b/tm/03.userGuide/05.backgroundchecks.md @@ -8,17 +8,17 @@ From Umbraco V.9 you cannot edit these settings directly via the backoffice, you By default Translation Manager will check the status of submitted jobs every 10 minutes. For some [Connectors](../reference/fundementals/connector) this will mean contacting their API and requesting the status of each job. -You can change this default behavior in the [Global Settings](../reference/global) of Translation manager. +You can change this default behavior in the [Global Settings](../reference/global) of Translation Manager. ![Background settings](background.png) -- Background Check - Turn off to stop checking completely. -- Check Period - How may seconds between checks. +- Background Check - Turn this setting off to stop checking completely. +- Check Period - Change how many seconds there are between checks. -:::caution -If you turn off background checking all jobs will have to be manually checked to progress between submitted and received. +:::danger Remember.. +If you turn off background checking, all jobs will have to be manually checked to progress between submitted and received. ::: \ No newline at end of file diff --git a/tm/03.userGuide/10.notifications.md b/tm/03.userGuide/10.notifications.md index 550d122..dc5d92c 100644 --- a/tm/03.userGuide/10.notifications.md +++ b/tm/03.userGuide/10.notifications.md @@ -3,7 +3,7 @@ title: Get Email Notifications --- :::warning Not Available In This Version -From Umbraco v.9 you cannot edit these settings directly via the backoffice, you must update these settings in the `AppSetting.json` file +From Umbraco v.9 you cannot edit these settings directly via the backoffice, you must update these settings in the `AppSetting.json` file. ::: You can setup email notifications to get emails when jobs pass certain stages in Translation Manager. diff --git a/tm/04.Extending/01.connectors/02.XLIFF/01.config.md b/tm/04.Extending/01.connectors/02.XLIFF/01.config.md index 19ab839..b66ec12 100644 --- a/tm/04.Extending/01.connectors/02.XLIFF/01.config.md +++ b/tm/04.Extending/01.connectors/02.XLIFF/01.config.md @@ -24,7 +24,7 @@ If you do change the extension, you should be sure to tell your translation prov ## Advanced options If you need finer control over the xliff file processing you can access the advanced settings dialog: -:::warning +::: You should only alter the advanced options if you understand the consequences on the produced XLIFF and how Translation Manager processes the XLIFF files. These options are only intended to help when your translation provider requests something specific in how the XLIFF should be formatted or processed. ::: @@ -55,7 +55,7 @@ The processing options control how any returned XLIFF files are processed | - | - | |Produce Multiple Files| This will generate an XLIFF file for each page, instead of for your whole site. | Overwrite Blank Targets | When an XLIFF file is returned if it is missing any `` values, Translation manager can use the value from the source as the target. This only works if the target does not need to be translated -| Match Languages | Should the languages defined in the XLIFF file match exactly those in Umbraco ? Most of the time this doesn't matter. You (or your provider) may have mapped the language codes to something else, as long as the translated text is as intended. +| Match Languages | Should the languages defined in the XLIFF file match exactly those in Umbraco? Most of the time this doesn't matter. You (or your provider) may have mapped the language codes to something else, as long as the translated text is as intended. | Language Mappings | Sometimes the languages you have installed on your site do not match exactly those supported by your translation company, for example your site might be setup in French (fr), but your translator expects French (France) (fr-fr). You can set a mapping here so when the file is processed it will send the language your translator is expecting. diff --git a/tm/04.Extending/01.connectors/05.Microsoft.md b/tm/04.Extending/01.connectors/05.Microsoft.md index 0545d10..bfe7a83 100644 --- a/tm/04.Extending/01.connectors/05.Microsoft.md +++ b/tm/04.Extending/01.connectors/05.Microsoft.md @@ -8,7 +8,7 @@ title: Microsoft Translator API It is a cloud-based machine translation service supporting multiple languages that reach more than 95% of the world's gross domestic product (GDP).Translator can be used to build applications, websites, tools, or any solution requiring multi-language support. ## API Key -in order to use Microsoft Translator API you will need an API Key. This API Key is received upon subscription to Microsoft Translator API. The API Key should be put in the API Key box. +In order to use Microsoft Translator API you will need an API Key. This API Key is received upon subscription to Microsoft Translator API. The API Key should be put in the API Key box. ## Endpoint In most cases the global endpoint should route to the nearest data center, but you can select a specific endpoint if necessary. diff --git a/tm/04.Extending/01.connectors/10.Smartcat.md b/tm/04.Extending/01.connectors/10.Smartcat.md index 58c150a..914199b 100644 --- a/tm/04.Extending/01.connectors/10.Smartcat.md +++ b/tm/04.Extending/01.connectors/10.Smartcat.md @@ -46,7 +46,7 @@ the Smartcat connector allows you to work with Smartcat projects in a number of > When using "Project per translation" or "Single project" some functionality, such as remove job, will not remove items from Smartcat. This is because removing the project could remove files from other translation jobs -### Default deadline. +### Default Deadline The default number of days from submission to set the translation deadline. Changing deadlines can effect costs and delivery. You should be clear with your translation project manager about the consequences of changing this value.