Other updates from feedback

Author: mthalman

Documentation/Renovate.md

@@ -55,9 +55,11 @@ For example, there are Dockerfiles in the [dotnet/dotnet-buildtools-prereqs-dock
 Protecting GitHub repositories in the dotnet organization from direct access by the Renovate tool is crucial.
 Renovate will be used in fork mode, limiting its permissions to forked repositories.
 This avoids giving write permissions to Renovate on any dotnet repository.
+This means that Renovate acts as though it's any other outside contributor, not requiring any special permissions in the dotnet organization or repositories.
+
 A GitHub bot account, `dotnet-renovate-bot`, is used to manage the Renovate operations.
 This account has the ability to create forks from dotnet repositories, which will be the source of the head branch for PRs that are created.
-
+The PRs generated by Renovate will be done using this bot account.
 GitHub scopes required by this account: `repo`, `workflow`.
 
 ### Repo Usage
@@ -67,6 +69,13 @@ This template handles the execution of Renovate, ensuring a standardized approac
 Repositories wishing to make use of Renovate can reference this template from a pipeline YAML file, setting the schedule trigger as desired.
 Consuming repositories are responsible for providing their own [Renovate configuration file](https://docs.renovatebot.com/configuration-options/) that describes which dependencies should be updated.
 
+Repositories are in control of how often Renovate will run via the pipeline schedule trigger (once a day, once a week, etc).
+Typically, a pipeline would be configured to update all dependencies at once in which case all dependencies are described in one Renovate config file.
+But in some cases, it may be desired to have certain dependencies updated on a different schedule than others.
+In that case, the repo maintainer would define multiple pipelines with those separate schedules, all configured to run Renovate.
+Importantly, each of those pipelines would need to reference a separate Renovate config file which defines the scope of the updates that will be targeted.
+Lastly, a maintainer is free to manually run the pipeline if an expected update is needed right away.
+
 ## Renovate Configuration Patterns
 
 TBD