Update Using Programmatic Views.md
Proofread and made changes.
MODIFY
.github/guides/Using Programmatic Views.md
.github/guides/Using Programmatic Views.md
@@ -6,7 +6,7 @@ The app in this guide is going to be very simple. It consists of a screen that
![Preview image of app](https://user-images.githubusercontent.com/79471462/131556322-56757c1d-e4ec-4581-a47c-969f536e3893.gif)
-## Adding the dependency
+## Adding the Dependency
For instructions on SPM and CocoaPods, [check out our installation page.](installation.html#swift-package-manager)
@@ -14,7 +14,7 @@ For instructions on SPM and CocoaPods, [check out our installation page.](instal
SwiftCurrent is so convenient that you may miss the couple lines that are calls to the library. To make it easier, we've marked our code snippets with `// SwiftCurrent` to highlight items that are coming from the library.
-## Create your view controllers
+## Create Your View Controllers
Create two view controllers that inherit from `UIWorkflowItem` and implement `FlowRepresentable`.
@@ -121,7 +121,7 @@ class SecondViewController: UIWorkflowItem<String, String>, FlowRepresentable {
}
```
-### Let's talk about what is going on with these view controllers
+### What Is Going on With These View Controllers?
#### **What's this `shouldLoad()`?**
@@ -171,9 +171,9 @@ class ViewController: UIViewController {
}
```
-### Let's discuss what's going on here
+### What Is Going on Here?
-#### **Where is the type safety, I heard about?**
+#### **Where is the type safety I heard about?**
<details>
@@ -196,12 +196,11 @@ Calling <code>Workflow.abandon()</code> closes all the views launched as part of
## Testing
-### Installing test dependencies
+### Installing Test Dependencies
-For our test example, we will be using a library called [UIUTest](https://github.com/nallick/UIUTest). It is optional for testing SwiftCurrent, but in order for the example to be copyable, you will need to add the UIUTest Swift Package
-to your test target.
+For our test example, we are using a library called [UIUTest](https://github.com/nallick/UIUTest). It is optional for testing SwiftCurrent, but in order for the example to be copyable, you will need to add the UIUTest Swift Package to your test target.
-### Creating tests
+### Creating Tests
```swift
import XCTest
@@ -251,26 +250,26 @@ class SecondViewControllerTests: XCTestCase {
While this team finds that testing our view controllers with [UIUTest](https://github.com/nallick/UIUTest) allows us to decrease the visibility of our properties and provide better coverage, [UIUTest](https://github.com/nallick/UIUTest) is not needed for testing SwiftCurrent. If you do not want to take the dependency, you will have to elevate visibility or find a way to invoke the `finishPressed` method.
-#### **What is going on with: `testSecondViewControllerDoesNotLoadWhenInputIsEmpty`?**
+#### **What is going on with `testSecondViewControllerDoesNotLoadWhenInputIsEmpty`?**
<details>
-This test is super simple. We create the view controller in a way that will go through the correct init, with expected arguments. Then we call <code>shouldLoad</code> to validate if the provided Input gets us the results we want.
+This test is super simple. We create the view controller in a way that will go through the correct init, with expected arguments. Then we call <code>shouldLoad</code> to validate if the provided input gets us the results we want.
</details>
-#### **What is going on with: `testProceedPassesThroughInput`?**
+#### **What is going on with `testProceedPassesThroughInput`?**
<details>
-At a high level we are loading the view controller for testing (similar to before but now with an added step of triggering lifecycle events). We update the <code>proceedInWorkflow</code> closure so that we can confirm it was called. Finally we invoke the method that will call proceed. The assert is verifying that the Output is the same as the input, as this view controller is passing it through.
+At a high level, we are loading the view controller for testing (similar to before but now with an added step of triggering lifecycle events). We update the <code>proceedInWorkflow</code> closure so that we can confirm it was called. Finally, we invoke the method that will call proceed. The assert is verifying that the output is the same as the input, as this view controller is passing it through.
</details>
#### **I added UIUTest, why isn't it hitting the finish button?**
<details>
-It's easy to forget to set the accessibility identifier on the button, please check that first. Second, if you don't call <code>loadForTesting()</code> your view controller doesn't make it to the window and the hit testing of <code>simulateTouch()</code> will also fail. Finally, make sure the button is visible and tappable on the simulator you are using.
+It's easy to forget to set the accessibility identifier on the button, please check that first. Second, if you don't call <code>loadForTesting()</code>, your view controller doesn't make it to the window and the hit testing of <code>simulateTouch()</code> will also fail. Finally, make sure the button is visible and tappable on the simulator you are using.
</details>
## Interoperability With SwiftUI
-You can use your SwiftUI `View`s that are `FlowRepresentable` in your UIKit workflows. Start with your `View`
+You can use your SwiftUI `View`s that are `FlowRepresentable` in your UIKit workflows. Start with your `View`.
```swift
import SwiftUI
@@ -286,7 +285,7 @@ struct SwiftUIView: View, FlowRepresentable { // SwiftCurrent
```
-Now in your UIKit workflow simply use a `HostedWorkflowItem`
+Now in your UIKit workflow, simply use a `HostedWorkflowItem`.
```swift
launchInto(Workflow(HostedWorkflowItem<SwiftUIView>.self)) // SwiftCurrent

Update Using Programmatic Views.md

Proofread and made changes.