Fix spelling: “Cocoapods” -> “CocoaPods”

Author: Clément Le Provost

ChangeLog.md

@@ -13,14 +13,14 @@ Change Log
 
 ## 3.2.1 (2016-05-27)
 
-- Fix OS X support in Cocoapods
+- Fix OS X support in CocoaPods
 
 
 ## 3.2 (2016-05-26)
 
 - Support iOS 7.0
-    - **Warning:** Because Cocoapods uses dynamic frameworks and Swift is not supported in dynamic frameworks on iOS 7,
-    iOS 7 support is not possible through Cocoapods.
+    - **Warning:** Because CocoaPods uses dynamic frameworks and Swift is not supported in dynamic frameworks on iOS 7,
+    iOS 7 support is not possible through CocoaPods.
     - **Warning:** Due to unavailability of simulators earlier than iOS 8.1 in Xcode 7.3, iOS 7 remains **untested**.
 - README updated
 - [Test] Add test case for DNS time-out

doc/maintenance.md

@@ -9,13 +9,13 @@
 The client exists in two different flavors:
 
 - The **online** flavor, which is the regular API client. Its source code is located under the `Source` directory. It
-  gets published to Cocoapods as `AlgoliaSearch-Client-Swift`.
+  gets published to CocoaPods as `AlgoliaSearch-Client-Swift`.
 
 - The **offline** flavor, which is a superset of the online flavor. In addition to the main source code, it adds the
-  `Source/offline` directory. It gets published to Cocoapods as `AlgoliaSearch-Offline-Swift`. This flavor has a
-  dependency on the Algolia Search Offline Core module (`AlgoliaSearchOfflineCore-iOS` in Cocoapods).
+  `Source/offline` directory. It gets published to CocoaPods as `AlgoliaSearch-Offline-Swift`. This flavor has a
+  dependency on the Algolia Search Offline Core module (`AlgoliaSearchOfflineCore-iOS` in CocoaPods).
 
-Cocoapods subspecs don't allow us to have different deployment platforms for each subspec. So, instead of using
+CocoaPods subspecs don't allow us to have different deployment platforms for each subspec. So, instead of using
 subspecs, we use **two distinct pods**.
 
 Although the project is published as two different pods, it is essentially the same code base. Therefore we wish to
@@ -36,11 +36,11 @@ keep versioning aligned (there is only one version number for both flavors).
 
 - **Dry-run the pod specs**: `pod lib lint` to check that everything's fine.
 
-    WARNING: Cocoapods is a very susceptible beast, and Xcode (used behind the scenes for building) add its own layer
+    WARNING: CocoaPods is a very susceptible beast, and Xcode (used behind the scenes for building) add its own layer
     of trouble on top of it. If you get weird, inexplicable behavior, try:
 
     - clearing Cocapods temporary directory (usually displayed in the error messages), which appears to be reused
-      between two invocations of Cocoapods;
+      between two invocations of CocoaPods;
 
     - clearing Xcode derived data in `~/Library/Developer/Xcode/DerivedData`.
 
@@ -54,8 +54,8 @@ keep versioning aligned (there is only one version number for both flavors).
 
     - `git push --tags origin master`
 
-- Make sure you have a **Cocoapods session** open: `pod trunk me`. If you have no active session, use
-  `pod trunk register EMAIL` to create one. (If you have never registered to Cocoapods, you need to contact one of
+- Make sure you have a **CocoaPods session** open: `pod trunk me`. If you have no active session, use
+  `pod trunk register EMAIL` to create one. (If you have never registered to CocoaPods, you need to contact one of
   the pod's owners; `pod trunk info` is your friend.)
 
 - **Publish the pods.** You have to publish each pod separately:
@@ -65,6 +65,6 @@ keep versioning aligned (there is only one version number for both flavors).
     - `pod trunk push --allow-warnings AlgoliaSearch-Offline-Swift.podspec`
 
     NOTE: Currently, `--allow-warnings` is required. We get warnings about useless conditional compilation on iOS 8.0,
-    but iOS 7 is really supported; it's just that it cannot be supported via Cocoapods.
+    but iOS 7 is really supported; it's just that it cannot be supported via CocoaPods.
 
 - Edit the **release notes**: in GitHub, edit the tag and copy-paste the Change Log section for this release.