Update notification host with right value

Also update readme

Author: vivangkumar

README.md

@@ -252,23 +252,10 @@ end
 
 Pusher now allows sending native notifications to iOS and Android devices. Check out the [documentation](https://pusher.com/docs/push_notifications) for information on how to set up push notifications on Android and iOS. There is no additional setup required to use it with this library. It works out of the box wit the same Pusher instance. All you need are the same pusher credentials.
 
-You can set the `notification_host` globally like so
-
-```ruby
-Pusher.notification_host = "<host>.com"
-```
-The default host is set to `<insert endpoint here>` and is currently the only supported host.
-
-Alternatively, you may set it on an instance of Pusher
-
-```ruby
-pusher.notification_host = "<host>.com"
-```
-
-You can also set a scheme for the notification host like above by specifying the `notification_scheme` key in the options hash or by setting it globally.
-
 ### Sending native pushes
 
+The native notifications API is hosted at `nativepush-cluster1.pusher.com` and only accepts https requests.
+
 You can send pushes by using the `notify` method, either globally or on the instance. The method takes two parameters:
 
 - `interests`: An Array of strings which represents the interests your devices are subscribed to. These are akin to channels in the DDN with less of an epehemeral nature. Note that currently, you can only send to _one_ interest.
@@ -279,17 +266,17 @@ Example:
 ```ruby
 data = {
   apns: {
-    alert: {
-      body: 'tada'
+    aps: {
+      alert: {
+        body: 'tada'
+      }
     }
   }
 }
 
 pusher.notify(["my-favourite-interest"], data)
 ```
 
-You may similarly use this method globally too.
-
 ### Errors
 
 Push notification requests, once submitted to the service are executed asynchronously. To make reporting errors easier, you can supply a `webhook_url` field in the body of the request. This will be used by the service to send a webhook to the supplied URL if there are errors.
@@ -301,8 +288,10 @@ For example:
 ```ruby
 data = {
   apns: {
-    alert: {
-      body: "hello"
+    aps: {
+      alert: {
+        body: "hello"
+      }
     }
   },
   gcm: {

lib/pusher/client.rb

@@ -34,7 +34,7 @@ def initialize(options = {})
 
       # TODO: Change host name when finalized
       merged_options[:notification_host] =
-        options.fetch(:notification_host, "hedwig-staging.herokuapp.com")
+        options.fetch(:notification_host, "nativepush-cluster1.pusher.com")
 
       merged_options[:notification_scheme] =
         options.fetch(:notification_scheme, "https")

spec/client_spec.rb

@@ -538,7 +538,7 @@
       end
 
       it "should use the default host if not provided" do
-        expect(@client.notification_host).to eq("hedwig-staging.herokuapp.com")
+        expect(@client.notification_host).to eq("nativepush-cluster1.pusher.com")
       end
 
       it "should use a newly provided host" do
@@ -632,7 +632,7 @@
       end
 
       it "should send a request to the notifications endpoint" do
-        notification_host_regexp = %r{hedwig-staging.herokuapp.com}
+        notification_host_regexp = %r{nativepush-cluster1.pusher.com}
         payload = {
           interests: ["test"],
           gcm: {
@@ -657,7 +657,7 @@
       end
 
       it "should delete restricted gcm keys before sending a notification" do
-        notification_host_regexp = %r{hedwig-staging.herokuapp.com}
+        notification_host_regexp = %r{nativepush-cluster1.pusher.com}
         payload = {
           interests: ["test"],
           gcm: {