svn commit: r1713651 - /olingo/site/trunk/content/doc/odata4/tutorials/batch/tutorial_batch.mdtext

[ch...@apache.org]

Author: chrish
Date: Tue Nov 10 14:45:53 2015
New Revision: 1713651

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

Modified:
    olingo/site/trunk/content/doc/odata4/tutorials/batch/tutorial_batch.mdtext

Modified: olingo/site/trunk/content/doc/odata4/tutorials/batch/tutorial_batch.mdtext
URL: http://svn.apache.org/viewvc/olingo/site/trunk/content/doc/odata4/tutorials/batch/tutorial_batch.mdtext?rev=1713651&r1=1713650&r2=1713651&view=diff
==============================================================================
--- olingo/site/trunk/content/doc/odata4/tutorials/batch/tutorial_batch.mdtext (original)
+++ olingo/site/trunk/content/doc/odata4/tutorials/batch/tutorial_batch.mdtext Tue Nov 10 14:45:53 2015
@@ -42,7 +42,7 @@ This tutorial can be found in subdirecto
 # 1. Introduction
 
 Batch requests [(OData Version 4.0 Part 1: Protocol Plus Errata 02)](http://docs.oasis-open.org/odata/odata/v4.0/errata02/os/complete/part1-protocol/odata-v4.0-errata02-os-part1-protocol-complete.html#_Toc406398359) allow grouping multiple operations into a single HTTP request payload. A batch request is represented as a Multipart MIME v1.0 message [(RFC2046)](https://www.ietf.org/rfc/rfc2046.txt).
-Each part of a Multipart MINE message can have a differtent content type. For example you can mix OData requests with Content-Type an `application/json` and Media Ressource Requests with Content Type `image/png`.
+Each part of a Multipart MINE message can have a differtent content type. For example you can mix OData requests with Content-Type `application/json` and Media Ressource Requests with Content Type `image/png`.
 
 The content of batch requests can consist of a series of individual requests and Change Sets, each represented as a distinct MIME part. In difference to OData V2 an individual request can be a Data Request, Data Modification Request, Action invocation request or a Function invocation request. So all kinds of OData requests are allowed at top level. The order of individual requests and Change Set sets in significant. Within a Change Set you can use Data Modification requests and Action invocation requests. Due to the fact that all requests within a Change Set are unordered, GET requests must not be used within a Change Set. All operations in a change set represent a single change unit so a service must successfully process and apply all the requests in the change set or else apply none of them.