[UNOMI-564] - Misinformation in some descriptions in online site docs (#409)
* trivial fixes in manual
* UNOMI-564 : fixing community links
* UNOMI-564 : periods to re-run integ-tests
diff --git a/manual/src/archives/1.5/asciidoc/connectors/connectors.adoc b/manual/src/archives/1.5/asciidoc/connectors/connectors.adoc
index b15e5ca..4d9ac82 100644
--- a/manual/src/archives/1.5/asciidoc/connectors/connectors.adoc
+++ b/manual/src/archives/1.5/asciidoc/connectors/connectors.adoc
@@ -22,4 +22,4 @@
==== Call for contributors
We are looking for help with the development of additional connectors. Any contribution (large or small) is more than
-welcome. Feel free to discuss this in our link:http://unomi.apache.org/community.html[mailing list, window="_blank"].
\ No newline at end of file
+welcome. Feel free to discuss this in our link:http://unomi.apache.org/community/[mailing list, window="_blank"].
\ No newline at end of file
diff --git a/manual/src/archives/1.5/asciidoc/datamodel.adoc b/manual/src/archives/1.5/asciidoc/datamodel.adoc
index 0d97d43..8f04857 100755
--- a/manual/src/archives/1.5/asciidoc/datamodel.adoc
+++ b/manual/src/archives/1.5/asciidoc/datamodel.adoc
@@ -194,7 +194,7 @@
|===
| *Field* | *Type* | *Description*
-| eventType | String | Contains an identifier for the field type, which may be any value as Apache Unomi does not come with strict event type definitions and accepts custom events types. The system comes with built-in event types such as “view”, “form”, “login”, “updateProperties” but additional event types may of course be used by developers integrating with Apache Unomi.
+| eventType | String | Contains an identifier for the event type, which may be any value as Apache Unomi does not come with strict event type definitions and accepts custom events types. The system comes with built-in event types such as “view”, “form”, “login”, “updateProperties” but additional event types may of course be used by developers integrating with Apache Unomi.
| sessionId | String | The unique identifier of a Session object
@@ -415,7 +415,7 @@
| typeIdentifier | String | This is a unique consent type identifier, basically a unique name for the consent. Example of such types might include: “newsletter”, “personalization”, “tracking”.
-| status | GRANTED / DENIED / REVOKED | A copy of the profile associated with the session
+| status | GRANTED / DENIED / REVOKED | The type of status for this consent
| statusDate | Date | The date (in ISO 8601 format) at which the current status was set
@@ -1066,7 +1066,7 @@
|===
| *Field name* | *Type* | *Description*
-| elements | ScoringElement array | A ScoringElement is composed of:* A Condition* A Score increment valueEach element defines a separate condition (tree) that will increment the defined score for this scoring plan, making it possible to have completely different conditions to augment a score
+| elements | ScoringElement array | A ScoringElement is composed of: a Condition and a score value to increment. Each element defines a separate condition (tree) that will increment the defined score for this scoring plan, making it possible to have completely different conditions to augment a score.
|===
diff --git a/manual/src/archives/1.6/asciidoc/connectors/connectors.adoc b/manual/src/archives/1.6/asciidoc/connectors/connectors.adoc
index b15e5ca..4d9ac82 100644
--- a/manual/src/archives/1.6/asciidoc/connectors/connectors.adoc
+++ b/manual/src/archives/1.6/asciidoc/connectors/connectors.adoc
@@ -22,4 +22,4 @@
==== Call for contributors
We are looking for help with the development of additional connectors. Any contribution (large or small) is more than
-welcome. Feel free to discuss this in our link:http://unomi.apache.org/community.html[mailing list, window="_blank"].
\ No newline at end of file
+welcome. Feel free to discuss this in our link:http://unomi.apache.org/community/[mailing list, window="_blank"].
\ No newline at end of file
diff --git a/manual/src/archives/1.6/asciidoc/datamodel.adoc b/manual/src/archives/1.6/asciidoc/datamodel.adoc
index 0d97d43..8f04857 100755
--- a/manual/src/archives/1.6/asciidoc/datamodel.adoc
+++ b/manual/src/archives/1.6/asciidoc/datamodel.adoc
@@ -194,7 +194,7 @@
|===
| *Field* | *Type* | *Description*
-| eventType | String | Contains an identifier for the field type, which may be any value as Apache Unomi does not come with strict event type definitions and accepts custom events types. The system comes with built-in event types such as “view”, “form”, “login”, “updateProperties” but additional event types may of course be used by developers integrating with Apache Unomi.
+| eventType | String | Contains an identifier for the event type, which may be any value as Apache Unomi does not come with strict event type definitions and accepts custom events types. The system comes with built-in event types such as “view”, “form”, “login”, “updateProperties” but additional event types may of course be used by developers integrating with Apache Unomi.
| sessionId | String | The unique identifier of a Session object
@@ -415,7 +415,7 @@
| typeIdentifier | String | This is a unique consent type identifier, basically a unique name for the consent. Example of such types might include: “newsletter”, “personalization”, “tracking”.
-| status | GRANTED / DENIED / REVOKED | A copy of the profile associated with the session
+| status | GRANTED / DENIED / REVOKED | The type of status for this consent
| statusDate | Date | The date (in ISO 8601 format) at which the current status was set
@@ -1066,7 +1066,7 @@
|===
| *Field name* | *Type* | *Description*
-| elements | ScoringElement array | A ScoringElement is composed of:* A Condition* A Score increment valueEach element defines a separate condition (tree) that will increment the defined score for this scoring plan, making it possible to have completely different conditions to augment a score
+| elements | ScoringElement array | A ScoringElement is composed of: a Condition and a score value to increment. Each element defines a separate condition (tree) that will increment the defined score for this scoring plan, making it possible to have completely different conditions to augment a score.
|===
diff --git a/manual/src/main/asciidoc/connectors/connectors.adoc b/manual/src/main/asciidoc/connectors/connectors.adoc
index b15e5ca..4d9ac82 100644
--- a/manual/src/main/asciidoc/connectors/connectors.adoc
+++ b/manual/src/main/asciidoc/connectors/connectors.adoc
@@ -22,4 +22,4 @@
==== Call for contributors
We are looking for help with the development of additional connectors. Any contribution (large or small) is more than
-welcome. Feel free to discuss this in our link:http://unomi.apache.org/community.html[mailing list, window="_blank"].
\ No newline at end of file
+welcome. Feel free to discuss this in our link:http://unomi.apache.org/community/[mailing list, window="_blank"].
\ No newline at end of file
diff --git a/manual/src/main/asciidoc/datamodel.adoc b/manual/src/main/asciidoc/datamodel.adoc
index 0d97d43..8f04857 100755
--- a/manual/src/main/asciidoc/datamodel.adoc
+++ b/manual/src/main/asciidoc/datamodel.adoc
@@ -194,7 +194,7 @@
|===
| *Field* | *Type* | *Description*
-| eventType | String | Contains an identifier for the field type, which may be any value as Apache Unomi does not come with strict event type definitions and accepts custom events types. The system comes with built-in event types such as “view”, “form”, “login”, “updateProperties” but additional event types may of course be used by developers integrating with Apache Unomi.
+| eventType | String | Contains an identifier for the event type, which may be any value as Apache Unomi does not come with strict event type definitions and accepts custom events types. The system comes with built-in event types such as “view”, “form”, “login”, “updateProperties” but additional event types may of course be used by developers integrating with Apache Unomi.
| sessionId | String | The unique identifier of a Session object
@@ -415,7 +415,7 @@
| typeIdentifier | String | This is a unique consent type identifier, basically a unique name for the consent. Example of such types might include: “newsletter”, “personalization”, “tracking”.
-| status | GRANTED / DENIED / REVOKED | A copy of the profile associated with the session
+| status | GRANTED / DENIED / REVOKED | The type of status for this consent
| statusDate | Date | The date (in ISO 8601 format) at which the current status was set
@@ -1066,7 +1066,7 @@
|===
| *Field name* | *Type* | *Description*
-| elements | ScoringElement array | A ScoringElement is composed of:* A Condition* A Score increment valueEach element defines a separate condition (tree) that will increment the defined score for this scoring plan, making it possible to have completely different conditions to augment a score
+| elements | ScoringElement array | A ScoringElement is composed of: a Condition and a score value to increment. Each element defines a separate condition (tree) that will increment the defined score for this scoring plan, making it possible to have completely different conditions to augment a score.
|===
diff --git a/wab/src/main/webapp/index.html b/wab/src/main/webapp/index.html
index 56363a7..93a0f25 100644
--- a/wab/src/main/webapp/index.html
+++ b/wab/src/main/webapp/index.html
@@ -79,7 +79,7 @@
</li>
<li>Try out some <a href="http://unomi.apache.org/manual/latest/index.html#_integration_samples"
target="_blank">samples</a></li>
- <li>Join <a href="http://unomi.apache.org/community.html" target="_blank">Apache Unomi's mailing lists</a></li>
+ <li>Join <a href="http://unomi.apache.org/community/" target="_blank">Apache Unomi's mailing lists</a></li>
<li>Star the project on Github <!-- Place this tag where you want the button to render. -->
<a class="github-button" href="https://github.com/apache/incubator-unomi" data-icon="octicon-star"
data-show-count="true" aria-label="Star apache/incubator-unomi on GitHub">Star</a>
