From 1cb6857193d6353691058130365d98731bce1f4e Mon Sep 17 00:00:00 2001 From: "Douglas C. R. Paes" Date: Wed, 20 May 2020 16:15:22 -0300 Subject: [PATCH] Fixed some typos --- _documentation/authentication.md | 2 +- _howto/executions.md | 2 +- _howto/property_expression_mapping.md | 2 +- 3 files changed, 3 insertions(+), 3 deletions(-) diff --git a/_documentation/authentication.md b/_documentation/authentication.md index 49b4ce0..a22e650 100644 --- a/_documentation/authentication.md +++ b/_documentation/authentication.md @@ -17,7 +17,7 @@ content_markdown: |- X.509 Certificate Authentication. {: .error } - For Alfresco Audit audit, we use the same authentication that you already have in your Alfresco autehntication chain. And for Alfresco live workspace data, we use the authentication mechanism you have in place + For Alfresco Audit audit, we use the same authentication that you already have in your Alfresco authentication chain. And for Alfresco live workspace data, we use the authentication mechanism you have in place between SOLR and Alfresco. left_code_blocks: diff --git a/_howto/executions.md b/_howto/executions.md index 7488e46..c1ff8fd 100644 --- a/_howto/executions.md +++ b/_howto/executions.md @@ -8,7 +8,7 @@ parameters: content_markdown: |- An execution is a command that will be used to write the data to the target storage. Peltas supports different type of targets such as databases, SOLR, Elastic Search, CSV files, flat files, etc ... - Each data writer consist of its own specific configuration + Each data writer consists of its own specific configuration {: .warning} Executions could be chained and each previous execution data is available in the next one (i.e. for referential integrity). diff --git a/_howto/property_expression_mapping.md b/_howto/property_expression_mapping.md index 9673882..b34aafa 100644 --- a/_howto/property_expression_mapping.md +++ b/_howto/property_expression_mapping.md @@ -3,7 +3,7 @@ title: Expressions position: 1.3 description: Expression property mapping content_markdown: |- - Peltas expressions can be seen as virtual properties. Where an expression property always references a mapped property and provides a facility to change the format or convert the data value. The property has to be prefixed with prop: in oprder to be considered as an expression and it has to reference a preivously configured property. + Peltas expressions can be seen as virtual properties. Where an expression property always references a mapped property and provides a facility to change the format or convert the data value. The property has to be prefixed with prop: in order to be considered as an expression and it has to reference a previously configured property. left_code_blocks: - code_block: |- peltas.documentcreated.mapper.property.createdFormatted.data=prop:created