README.md in testcentricity_mobile-4.0.6 vs README.md in testcentricity_mobile-4.0.7

@@ -506,19 +506,20 @@
 Supported `AppUIElement` elementTypes and their declarations have the following format:
 
 *Single element declarations:*
 ```ruby
     class SampleScreen < TestCentricity::ScreenObject
-      button     :button_name, { locator_strategy: locator_identifier }
-      textfield  :field_name, { locator_strategy: locator_identifier }
-      checkbox   :checkbox_name, { locator_strategy: locator_identifier }
-      label      :label_name, { locator_strategy: locator_identifier }
-      list       :list_name, { locator_strategy: locator_identifier }
-      image      :image_name, { locator_strategy: locator_identifier }
-      switch     :switch_name, { locator_strategy: locator_identifier }
-      element    :element_name, { locator_strategy: locator_identifier }
-      alert      :alert_name, { locator_strategy: locator_identifier }
+      button    :button_name, { locator_strategy: locator_identifier }
+      textfield :field_name, { locator_strategy: locator_identifier }
+      checkbox  :checkbox_name, { locator_strategy: locator_identifier }
+      radio     :radio_name, { locator_strategy: locator_identifier }
+      label     :label_name, { locator_strategy: locator_identifier }
+      list      :list_name, { locator_strategy: locator_identifier }
+      image     :image_name, { locator_strategy: locator_identifier }
+      switch    :switch_name, { locator_strategy: locator_identifier }
+      element   :element_name, { locator_strategy: locator_identifier }
+      alert     :alert_name, { locator_strategy: locator_identifier }
     end
 ```
 *Multiple element declarations:*
 ```ruby
     class SampleScreen < TestCentricity::ScreenObject
@@ -529,10 +530,12 @@
                  field_2_name: { locator_strategy: locator_identifier },
                  field_X_name: { locator_strategy: locator_identifier }
       checkboxes check_1_name: { locator_strategy: locator_identifier },
                  check_2_name: { locator_strategy: locator_identifier },
                  check_X_name: { locator_strategy: locator_identifier }
+      radios     radio_1_name: { locator_strategy: locator_identifier },
+                 radio_X_name: { locator_strategy: locator_identifier }
       labels     label_1_name: { locator_strategy: locator_identifier },
                  label_X_name: { locator_strategy: locator_identifier }
       images     image_1_name: { locator_strategy: locator_identifier },
                  image_X_name: { locator_strategy: locator_identifier }
     end
@@ -591,11 +594,11 @@
 above) for each `AppUIElement` that needs to be interacted with.
 
 The `ScreenObject.populate_data_fields` and `ScreenSection.populate_data_fields` methods support the entry of test data
 into a collection of `AppUIElements`. The `populate_data_fields` method accepts a hash containing key/hash pairs of
 `AppUIElements` and their associated data to be entered. Data values must be in the form of a `String` for `textfield`
-controls. For `checkbox` controls, data must either be a `Boolean` or a `String` that evaluates to a `Boolean` value (Yes,
-No, 1, 0, true, false).
+controls. For `checkbox`, `radio`, and `switch` controls, data must either be a `Boolean` or a `String` that evaluates to
+a `Boolean` value ('Yes', 'No', '1', '0', 'true', 'false').
 
 The `populate_data_fields` method verifies that data attributes associated with each `AppUIElement` is not `nil` or `empty`
 before attempting to enter data into the `AppUIElement`.
 
 The optional `wait_time` parameter is used to specify the time (in seconds) to wait for each `AppUIElement` to become