svn commit: r1707007 - /olingo/site/trunk/content/doc/odata4/tutorials/action/tutorial_action.mdtext

[ch...@apache.org]

Author: chrish
Date: Tue Oct  6 11:39:45 2015
New Revision: 1707007

URL: http://svn.apache.org/viewvc?rev=1707007&view=rev
Log:
CMS commit to olingo by chrish

Modified:
    olingo/site/trunk/content/doc/odata4/tutorials/action/tutorial_action.mdtext

Modified: olingo/site/trunk/content/doc/odata4/tutorials/action/tutorial_action.mdtext
URL: http://svn.apache.org/viewvc/olingo/site/trunk/content/doc/odata4/tutorials/action/tutorial_action.mdtext?rev=1707007&r1=1707006&r2=1707007&view=diff
==============================================================================
--- olingo/site/trunk/content/doc/odata4/tutorials/action/tutorial_action.mdtext (original)
+++ olingo/site/trunk/content/doc/odata4/tutorials/action/tutorial_action.mdtext Tue Oct  6 11:39:45 2015
@@ -180,14 +180,14 @@ Create the following constants in the De
 	// Function/Action Parameters
 	public static final String PARAMETER_AMOUNT = "Amount";
 
-The way to announce the operations is very similar to announcing EntityTypes. We have to override some methods. Those methods provides the definition of the Edm elements. We need methods for:
+The way to announce the operations is very similar to announcing EntityTypes. We have to override some methods. Those methods provide the definition of the Edm elements. We need methods for:
 
  - Actions
  - Functions
  - Action Imports
  - Function Imports
 
-The code is simple and straight forward. First, we check which function we have to return. Then, a list of parameters and the return type are created. At the end the fit all parts together and return a new *CsdlFunction* Object.
+The code is simple and straight forward. First, we check which function we have to return. Then, a list of parameters and the return type are created. At the end all parts are fit together and get returned as new *CsdlFunction* Object.
 	
 	::::java
 	@Override
@@ -279,7 +279,7 @@ The code to define the actions and the a
 		return null;
 	}
 
-The last thing to do is we have to announce these operations to the schema and the entity container.
+Finally we have to announce these operations to the schema and the entity container.
 Add the following lines to the method *getSchemas()*:
 
 	::::java
@@ -413,7 +413,7 @@ The recent implementation of the *readEn
 		}
 	}
 
-Like by reading entity collections, the first step is to analyze the URI and read the data of the function import.
+Like reading entity collections, the first step are analyze the URI and read the data (of the function import).
 
 	::::java
 	private void readFunctionImportCollection(final ODataRequest request, final ODataResponse response, 
@@ -431,7 +431,7 @@ Like by reading entity collections, the
 		final UriResourceFunction uriResourceFunction = (UriResourceFunction) firstSegment;
 		final EntityCollection entityCol = storage.readFunctionImportCollection(uriResourceFunction, serviceMetadata);
 
-Then the result has to be serialized. The only difference to entity sets if the way how the Edm Entity Type is determined.
+Then the result has to be serialized. The only difference to entity sets is the way how the Edm Entity Type is determined.
 
 	::::java
 		// 2nd step: Serialize the response entity
@@ -544,7 +544,7 @@ Then deserialize the action parameters.
 														 		  .getActionParameters();
 		final Parameter parameterAmount = actionParameter.get(DemoEdmProvider.PARAMETER_AMOUNT);
 
-Execute the action and set the response code
+Execute the action and set the response code.
 
 	::::java
 		// The parameter amount is nullable