From 809c0dabc50e855eb44a34e0271a25e62388f2d0 Mon Sep 17 00:00:00 2001 From: Drew Olbrich Date: Sun, 10 Feb 2019 08:34:25 -0800 Subject: [PATCH] Update background --- README.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/README.md b/README.md index 38d89f8..d4dba71 100644 --- a/README.md +++ b/README.md @@ -35,7 +35,7 @@ This case can be handled by nesting the view inside a scroll view. You could do To simplify this task, ScrollingContentViewController inserts the scroll view into the view hierarchy for you at run time, along with all necessary Auto Layout constraints. -When used in a storyboard, ScrollingContentViewController exposes a [`contentView`](#contentView) outlet that you connect to the view that you'd like make scrollable. Everything else is taken care of automatically, including keyboard presentation and device orientation changes. +When used in a storyboard, ScrollingContentViewController exposes an outlet called [`contentView`](#contentView) that you connect to the view that you'd like to make scrollable. This may be the view controller's root view. Everything else is taken care of automatically, including keyboard presentation and device orientation changes. ScrollingContentViewController can be configured using storyboards or entirely in code. The easiest way to use it is by subclassing the `ScrollingContentViewController` class instead of [`UIViewController`](https://developer.apple.com/documentation/uikit/uiviewcontroller). However, when this is not an option, a helper class called `ScrollingContentViewManager` can be composed with your existing view controller class instead.