Have consistent capitalized Swift Package Manager name in docs

Author: federicobucchi

Documentation/EvolutionIdeas.md

@@ -59,7 +59,7 @@ Bug: [SR-883](https://bugs.swift.org/browse/SR-883)
 
 ## Resource Support
 
-The Swift package manager needs a story for how packages should specify their
+The Swift Package Manager needs a story for how packages should specify their
 resources to include with products.
 
 Thread: N/A

Documentation/Internals/README.md

@@ -1,6 +1,6 @@
 # Swift Package Manager Developer Docs
 
-This directory contains documentation on the engineering design decisions and internals of the Swift package manager. It is primarily focused at developers interested in working on the Swift package manager, but may also be useful to advanced users wanting to understand exactly how the package manager behaves.
+This directory contains documentation on the engineering design decisions and internals of the Swift Package Manager. It is primarily focused at developers interested in working on the Swift Package Manager, but may also be useful to advanced users wanting to understand exactly how the package manager behaves.
 
 * [Swift-based Manifest Format](SwiftBasedManifestFormat.md)
 

Documentation/PackageDescription.md

@@ -277,7 +277,7 @@ you can find the `Package.resolved` file inside your `.xcodeproj` or `.xcworkspa
 /// while making sure you don't update to a version with breaking changes,
 /// and helps to prevent conflicts in your dependency graph.
 ///
-/// The following example allows the Swift package manager to select a version
+/// The following example allows the Swift Package Manager to select a version
 /// like a  `1.2.3`, `1.2.4`, or `1.3.0`, but not `2.0.0`.
 ///
 ///    .package(url: "https://example.com/example-package.git", from: "1.2.3"),
@@ -299,7 +299,7 @@ static func package(url: String, _ requirement: Package.Dependency.Requirement)
 /// Add a package dependency starting with a specific minimum version, up to
 /// but not including a specified maximum version.
 ///
-/// The following example allows the Swift package manager to pick
+/// The following example allows the Swift Package Manager to pick
 /// versions `1.2.3`, `1.2.4`, `1.2.5`, but not `1.2.6`.
 ///
 ///     .package(url: "https://example.com/example-package.git", "1.2.3"..<"1.2.6"),
@@ -313,7 +313,7 @@ static func package(url: String, _ range: Range<Version>) -> Package.Dependency
 /// Add a package dependency starting with a specific minimum version, going
 /// up to and including a specific maximum version.
 ///
-/// The following example allows the Swift package manager to pick
+/// The following example allows the Swift Package Manager to pick
 /// versions 1.2.3, 1.2.4, 1.2.5, as well as 1.2.6.
 ///
 ///     .package(url: "https://example.com/example-package.git", "1.2.3"..."1.2.6"),

README.md

@@ -115,7 +115,7 @@ If you are interested in contributing, please read the [Community Proposal](Docu
 
 Instructions for setting up the development environment are available [here](Documentation/Development.md).
 
-The Swift package manager uses [llbuild](https://github.com/apple/swift-llbuild) as the underlying build system for compiling source files.  It is also open source and part of the Swift project.
+The Swift Package Manager uses [llbuild](https://github.com/apple/swift-llbuild) as the underlying build system for compiling source files.  It is also open source and part of the Swift project.
 
 ---
 

Sources/PackageDescription/Target.swift

@@ -684,7 +684,7 @@ extension Target.Dependency {
     /// - parameters:
     ///   - name: The name of the dependency, either a target or a product.
     ///
-    /// The Swift package manager creates the by-name dependency after it has loaded the package graph.
+    /// The Swift Package Manager creates the by-name dependency after it has loaded the package graph.
     @available(_PackageDescription, obsoleted: 5.3)
     public static func byName(name: String) -> Target.Dependency {
       #if PACKAGE_DESCRIPTION_4