From eff925f16824536dc19027ff11324b086aaf0b55 Mon Sep 17 00:00:00 2001
From: Allan Jardine <allan.jardine@sprymedia.co.uk>
Date: Thu, 6 Aug 2015 20:40:12 +0100
Subject: [PATCH] Fix - examples: Pipelining description had a typo

---
 .datatables-commit-sync            | 2 +-
 examples/server_side/pipeline.html | 2 +-
 2 files changed, 2 insertions(+), 2 deletions(-)

diff --git a/.datatables-commit-sync b/.datatables-commit-sync
index ee854819..e42e57d1 100644
--- a/.datatables-commit-sync
+++ b/.datatables-commit-sync
@@ -1 +1 @@
-bcf5444bdcfef350afcb7292461346b60dadd6f5
+20593c240c39855db99dc4f70f1801906f5a7859
diff --git a/examples/server_side/pipeline.html b/examples/server_side/pipeline.html
index 533f2a06..0fff5eb6 100644
--- a/examples/server_side/pipeline.html
+++ b/examples/server_side/pipeline.html
@@ -158,7 +158,7 @@ $(document).ready(function() {
 			<h1>DataTables example <span>Pipelining data to reduce Ajax calls for paging</span></h1>
 
 			<div class="info">
-				<p>Sever-side processing can be quite hard on your server, since it makes an Ajax call to the server for every draw request that is made. On sites with a large
+				<p>Server-side processing can be quite hard on your server, since it makes an Ajax call to the server for every draw request that is made. On sites with a large
 				number of page views, you could potentially end up DDoSing your own server with your own applications!</p>
 
 				<p>This example shows one technique to reduce the number of Ajax calls that are made to the server by caching more data than is needed for each draw. This is done