README.md in ctws-0.1.8.alpha vs README.md in ctws-0.1.9.alpha

@@ -54,10 +54,13 @@
 
 By default the user model is `User` but you can change it by creating or editing the `ctws.rb` initializer file in `config/initializers` and put this content in it:
 
 ```ruby 
 Ctws.user_class = "Account"
+
+Ctws.device_class = "DeviceApp" # TODO: documentation
+Ctws.profile_class = "Profile" # TODO: documentation
 ```
 
 The application `User` model **must have the `email` attribute**.
 
 The **`password` is optional** by default a user is validated with password, for `password` validation [`ActiveModel::SecurePassword::InstanceMethodsOnActivation authenticate`](https://apidock.com/rails/v4.2.7/ActiveModel/SecurePassword/InstanceMethodsOnActivation/authenticate) and [`Devise::Models::DatabaseAuthenticatable#valid_password?`](http://www.rubydoc.info/github/plataformatec/devise/Devise%2FModels%2FDatabaseAuthenticatable:valid_password%3F) User instance methods are supported.
@@ -68,10 +71,10 @@
 Ctws.user_validate_with_password = false
 ```
 You can edit your app's required fields for signup by creating or editing the `ctws.rb` initializer file in `config/initializers` and put your strong parameters:
 
 ```ruby 
-Ctws.user_class_strong_params = %i(email password password_confirmation
+Ctws.user_class_strong_params = [:email, :password, :password_confirmation]
 ```
 
 ### Set the `JWT` expiry time
 
 By default the token expiry time is 24h but you can change it by creating or editing the `ctws.rb` initializer file in `config/initializers` and put this content in it: