Adjust documentation

Author: wtmoose

SwiftMessages/SwiftMessagesSegue.swift

@@ -34,11 +34,18 @@ import UIKit
 
      dismiss(animated: true, completion: nil)
 
- To display the view controller in a new window, supply an instance of `WindowViewController` as the `source`.
-
  It is not necessary to retain `segue` because it retains itself until dismissal. However, you can
  retain it if you plan to `perform()` more than once.
 
+ #### Present the controller on top of all controllers
+
+ If you don't know the presenter or you don't want to pass it as a source, like when you
+ have a completely separated message controller, you can pass a `WindowViewController`
+ as the `source` argument of the segue's initializer.
+
+ By default, the window will be shown in the current window scene at `.normal` window level.
+ However, these parameters can be customized by initializing the view controller with a `SwiftMessages.Config` that has the `SwiftMessages.Config.presentationContext` set to either `.window` or `.windowScene`:
+
  + note: Some additional details:
  1. Your view controller's view will be embedded in a `SwiftMessages.BaseView` in order to
  utilize some SwiftMessages features. This view can be accessed and configured via the

ViewControllers.md

@@ -23,26 +23,32 @@ let segue = SwiftMessagesSegue(identifier: nil, source: self, destination: desti
 segue.perform()
 ````
 
+To dismiss, call the UIKit API on the presenting view controller:
+
+````swift
+dismiss(animated: true, completion: nil)
+````
+
+It is not necessary to retain `segue` because it retains itself until dismissal. However, you can retain it if you plan to `perform()` more than once.
+
 #### Present the controller on top of all controllers
 
-If you don't know the presenter or you don't want to pass it as a source like when you have a completely separated message controller, you can pass a `WindowViewController` as the **source** argument of the segue. Also, You can set  the `windowLevel` and other configurations by passing a config: `SwiftMessages.Config` instance as the argument of the `WindowViewController`:
+If you don't know the presenter or you don't want to pass it as a source, like when you
+have a completely separated message controller, you can pass a `WindowViewController`
+as the `source` argument of the segue's initializer.
+
+By default, the window will be shown in the current window scene at `.normal` window level.
+However, these parameters can be customized by initializing the view controller with a `SwiftMessages.Config` that has the `SwiftMessages.Config.presentationContext` set to either `.window` or `.windowScene`:
 
 ```swift
 let destinationVC = ... // make a reference to a destination view controller
-let sourceVC = WindowViewController(config: SwiftMessages.defaultConfig) // The `config` can be any custom `SwiftMessages.Config` instance
+var config = SwiftMessages.defaultConfig
+config.presentationContext = .windowScene(...) // specify the window properties
+let sourceVC = WindowViewController(config: config)
 let segue = SwiftMessagesSegue(identifier: nil, source: self, destination: destinationVC)
-... // do any configuration here
 segue.perform()
 ```
 
-To dismiss, call the UIKit API on the presenting view controller:
-
-````swift
-dismiss(animated: true, completion: nil)
-````
-
-It is not necessary to retain `segue` because it retains itself until dismissal. However, you can retain it if you plan to `perform()` more than once.
-
 ### Configuration
 
 `SwiftMessagesSegue` generally requires configuration to achieve specific layouts and optional behaviors. There are a few good ways to do this: