svn commit: r1853782 - in /olingo/site/trunk/content/doc: odata2/download.mdtext odata2/tutorials/debug.mdtext odata4/tutorials/navigation/tutorial_navigation.mdtext odata4/tutorials/readep/tutorial_readep.mdtext

[mi...@apache.org]

Author: mibo
Date: Mon Feb 18 05:56:38 2019
New Revision: 1853782

URL: http://svn.apache.org/viewvc?rev=1853782&view=rev
Log:
[OLINGO-1339] Fixed typos

Modified:
    olingo/site/trunk/content/doc/odata2/download.mdtext
    olingo/site/trunk/content/doc/odata2/tutorials/debug.mdtext
    olingo/site/trunk/content/doc/odata4/tutorials/navigation/tutorial_navigation.mdtext
    olingo/site/trunk/content/doc/odata4/tutorials/readep/tutorial_readep.mdtext

Modified: olingo/site/trunk/content/doc/odata2/download.mdtext
URL: http://svn.apache.org/viewvc/olingo/site/trunk/content/doc/odata2/download.mdtext?rev=1853782&r1=1853781&r2=1853782&view=diff
==============================================================================
--- olingo/site/trunk/content/doc/odata2/download.mdtext (original)
+++ olingo/site/trunk/content/doc/odata2/download.mdtext Mon Feb 18 05:56:38 2019
@@ -30,9 +30,9 @@ The Apache Olingo OData2 2.0.11 release
 ### Commodity Packages
 
 The **Olingo Library Core** packages contains the *API*, the *implementation*, the *documentation as JavaDoc* and the *Reference Scenario*.
-The *API* and the according *implementation* can be used in a *productive* environment.
-The Reference Scenario is a sample and **shall not be used in a productive** environment.
-The *Core Library* is developed for the productive usage in business scenarios.
+The *API* and the according *implementation* can be used in a *production* environment.
+The Reference Scenario is a sample and **shall not be used in a production** environment.
+The *Core Library* is developed for production environment usage in business scenarios.
 
 Package | zip | Description
 ------- | --- | -----
@@ -46,7 +46,7 @@ Olingo OData2 Reference Scenario | [Down
 The **Olingo Library Extension** packages contains extensions which are provided from various contributors in the context of the Olingo open source project.
 The extensions provides convenience for easier consumption or creation of an OData service like the *JPA based processor*, the *Java Annotation based processor* or the *Spring Framework integration*.
 However the extensions are *not optimized regarding performance or extensibility*.
-Interested parties can use the extensions, if they are sufficient for their scenarios in a productive environment.
+Interested parties can use the extensions, if they are sufficient for their scenarios in a production environment.
 Feature enhancements or optimizations of the extensions have to be done by the interested parties itself.
 
 Package | zip | Description

Modified: olingo/site/trunk/content/doc/odata2/tutorials/debug.mdtext
URL: http://svn.apache.org/viewvc/olingo/site/trunk/content/doc/odata2/tutorials/debug.mdtext?rev=1853782&r1=1853781&r2=1853782&view=diff
==============================================================================
--- olingo/site/trunk/content/doc/odata2/tutorials/debug.mdtext (original)
+++ olingo/site/trunk/content/doc/odata2/tutorials/debug.mdtext Mon Feb 18 05:56:38 2019
@@ -33,7 +33,7 @@ The OData V2 error message format is lim
 
 Apache Olingo has implemented a feature to return more error information (stack traces, object states, runtime measurements …) within a response to ease the development and support use case.
 
-For productive uses cases this feature is by default off. The following explains how to enable the feature and gives options to a service implementation to switch if on and off e.g. role based or by configuration.
+For uses cases in a production environment this feature is by default off. The following explains how to enable the feature and gives options to a service implementation to switch if on and off e.g. role based or by configuration.
 
 ##### DebugCallback
 
@@ -189,7 +189,7 @@ is requested as described above.
 
 Apache Olingo has no dependencies to any specific log and trace api (e.g. slf4j, log4j …) and with that it does not trace anything by default. This is to keep the library independent from a specific api so that it can be used on any JEE compliant platform independent from which l&t api is offered there.
 
-Anyhow log and trace is required for productive use and the following recommendations are given:
+Anyhow log and trace is required for most production environments and the following recommendations are given:
 
 ##### Servlet Filter
 

Modified: olingo/site/trunk/content/doc/odata4/tutorials/navigation/tutorial_navigation.mdtext
URL: http://svn.apache.org/viewvc/olingo/site/trunk/content/doc/odata4/tutorials/navigation/tutorial_navigation.mdtext?rev=1853782&r1=1853781&r2=1853782&view=diff
==============================================================================
--- olingo/site/trunk/content/doc/odata4/tutorials/navigation/tutorial_navigation.mdtext (original)
+++ olingo/site/trunk/content/doc/odata4/tutorials/navigation/tutorial_navigation.mdtext Mon Feb 18 05:56:38 2019
@@ -895,7 +895,7 @@ Check the *Links* section for more OData
 
 # 7. Appendix: code snippets
 
-When reaching the point where your OData service has to become productive and support complex scenarions, you’ll find the following code snippets useful.
+When reaching the point where your OData service has to become production ready and support complex scenarions, you’ll find the following code snippets useful.
 
 ## 7.1. Find the EdmEntitySet for the navigation target
 

Modified: olingo/site/trunk/content/doc/odata4/tutorials/readep/tutorial_readep.mdtext
URL: http://svn.apache.org/viewvc/olingo/site/trunk/content/doc/odata4/tutorials/readep/tutorial_readep.mdtext?rev=1853782&r1=1853781&r2=1853782&view=diff
==============================================================================
--- olingo/site/trunk/content/doc/odata4/tutorials/readep/tutorial_readep.mdtext (original)
+++ olingo/site/trunk/content/doc/odata4/tutorials/readep/tutorial_readep.mdtext Mon Feb 18 05:56:38 2019
@@ -518,7 +518,7 @@ The steps to be followed in the implemen
         :::java
         UriResourceEntitySet uriResourceEntitySet = (UriResourceEntitySet) resourcePaths.get(0);
 
-    This is only possible, because in our current sample scenario we only support simple URIs. In a real productive OData service, which supports navigation and other OData V4 features, the code would be more complex.
+    This is only possible, because in our current sample scenario we only support simple URIs. In a real production environment OData service, which supports navigation and other OData V4 features, the code would be more complex.
 
   2. **Fetch the data from backend**  
     In the backend, which in our sample is represented by the `Storage` class, we have a list with products.