From 0058257db769517aae89afc2b0c8203c9cda3b3c Mon Sep 17 00:00:00 2001
From: Andrew Kane <acekane1@gmail.com>
Date: Sun, 15 Jan 2017 22:59:04 -0800
Subject: [PATCH] Renamed to parallel reindexing [skip ci]

---
 README.md | 8 +++-----
 1 file changed, 3 insertions(+), 5 deletions(-)

diff --git a/README.md b/README.md
index 739ea85..d7e3793 100644
--- a/README.md
+++ b/README.md
@@ -436,7 +436,7 @@ If a reindex is interrupted, you can resume it with:
 Product.reindex(resume: true)
 ```
 
-For large data sets, try [background reindexing](#background-reindexing).
+For large data sets, try [parallel reindexing](#parallel-reindexing).
 
 ### To Reindex, or Not to Reindex
 
@@ -1155,9 +1155,7 @@ class Product < ActiveRecord::Base
 end
 ```
 
-### Background Reindexing
-
-*ActiveRecord only*
+### Parallel Reindexing
 
 For large data sets, you can use background jobs to parallelize reindexing.
 
@@ -1186,7 +1184,7 @@ Searchkick.reindex_status(index_name)
 
 ### Queuing
 
-You can also queue ids of records that need reindexed and reindex in bulk for better performance. First, set up Redis in an initializer.
+Push ids of records needing reindexed to a queue and reindex in bulk for better performance. First, set up Redis in an initializer.
 
 ```ruby
 Searchkick.redis = Redis.new
--
libgit2 0.21.0