Fix punctuation (swiftlang#569)

Author: federicobucchi

_data/documentation.yaml

@@ -9,7 +9,7 @@
     url: /documentation/api-design-guidelines/
     description: |
       Delivering a clear, consistent developer experience when writing Swift code is largely defined by the names and idioms that appear in APIs.
-      These design guidelines explain how to make sure that your code feels like a part of the larger Swift ecosystem
+      These design guidelines explain how to make sure that your code feels like a part of the larger Swift ecosystem.
   - title: Standard Library
     url: /documentation/standard-library/
     description: |
@@ -38,7 +38,7 @@
   - title: Swift on Server
     url: /documentation/server/
     description: |
-      Swift is a general-purpose programming language with unique characteristics that make it specifically suitable for Server applications
+      Swift is a general-purpose programming language with unique characteristics that make it specifically suitable for Server applications.
   - title: Mixing Swift and C++
     url: /documentation/cxx-interop/
     description: |
@@ -83,4 +83,4 @@
   - title: Compiler Architecture
     url: /documentation/swift-compiler/
     description: |
-      Overview of the Swift compiler architecture
+      Overview of the Swift compiler architecture.

code-of-conduct/index.md

@@ -13,19 +13,19 @@ In the interest of fostering an open and welcoming environment, we as contributo
 
 Examples of behavior that contributes to creating a positive environment include:
 
-* Using welcoming and inclusive language (e.g., prefer non-gendered words like “folks” to “guys”, non-ableist words like “soundness check” to “sanity check”, etc.)
-* Being respectful of differing viewpoints and experiences
-* Gracefully accepting constructive criticism
-* Focusing on what is best for the community
-* Showing empathy towards other community members
+* Using welcoming and inclusive language (e.g., prefer non-gendered words like “folks” to “guys”, non-ableist words like “soundness check” to “sanity check”, etc.).
+* Being respectful of differing viewpoints and experiences.
+* Gracefully accepting constructive criticism.
+* Focusing on what is best for the community.
+* Showing empathy towards other community members.
 
 Examples of unacceptable behavior by participants include:
 
-* The use of sexualized language or imagery and unwelcome sexual attention or advances
-* Trolling, insulting/derogatory comments, and personal or political attacks
-* Public or private harassment
-* Publishing others’ private information, such as a physical or electronic address, without explicit permission
-* Other conduct which could reasonably be considered inappropriate in a professional setting
+* The use of sexualized language or imagery and unwelcome sexual attention or advances.
+* Trolling, insulting/derogatory comments, and personal or political attacks.
+* Public or private harassment.
+* Publishing others’ private information, such as a physical or electronic address, without explicit permission.
+* Other conduct which could reasonably be considered inappropriate in a professional setting.
 
 Project maintainers are responsible for clarifying the standards of acceptable behavior and are expected to take appropriate and fair corrective action in response to any instances of unacceptable behavior.
 

community/_forums.md

@@ -21,22 +21,22 @@ A core principle for the Swift project is that the community is an open and incl
 
 ### Swift Users
 [Using Swift]: #using-swift
-**[Using Swift](https://forums.swift.org/c/swift-users)** - For newcomers or those primarily interested in using the Swift language, it is best to start by engaging within the Using Swift category.  This area is intended for users to get help with or ask questions about Swift or its related tools and is not for discussion about work being done to the language itself. This category will accept email sent to: [email protected]
+**[Using Swift](https://forums.swift.org/c/swift-users)** - For newcomers or those primarily interested in using the Swift language, it is best to start by engaging within the Using Swift category.  This area is intended for users to get help with or ask questions about Swift or its related tools and is not for discussion about work being done to the language itself. This category will accept email sent to: [email protected].
 
 ### Development
 [Development]: #development
 
-**[Compiler](https://forums.swift.org/c/development/compiler)** - For developers to discuss the development and implementation of the Swift compiler, low-level runtime, and SourceKit.  This category will accept email sent to: [email protected]
+**[Compiler](https://forums.swift.org/c/development/compiler)** - For developers to discuss the development and implementation of the Swift compiler, low-level runtime, and SourceKit.  This category will accept email sent to: [email protected].
 
-**[Standard Library](http://forums.swift.org/c/development/stdlib)** - For developers to discuss the implementation of the Swift standard library.  This category will accept email sent to: [email protected]
+**[Standard Library](http://forums.swift.org/c/development/stdlib)** - For developers to discuss the implementation of the Swift standard library.  This category will accept email sent to: [email protected].
 
-**[Core Libraries](http://forums.swift.org/c/development/corelibs)** - For developers to discuss the implementation of the Swift core libraries.  This category will accept email sent to: [email protected]
+**[Core Libraries](http://forums.swift.org/c/development/corelibs)** - For developers to discuss the implementation of the Swift core libraries.  This category will accept email sent to: [email protected].
 
-**[LLDB](http://forums.swift.org/c/development/lldb)** - For developers to discuss the implementation of the Swift REPL and Swift-specific aspects of LLDB. This category will accept email sent to: [email protected]
+**[LLDB](http://forums.swift.org/c/development/lldb)** - For developers to discuss the implementation of the Swift REPL and Swift-specific aspects of LLDB. This category will accept email sent to: [email protected].
 
-**[Package Manager](http://forums.swift.org/c/development/SwiftPM)** - For developers to discuss the implementation of the Swift package manager. This category will accept email sent to: [email protected]
+**[Package Manager](http://forums.swift.org/c/development/SwiftPM)** - For developers to discuss the implementation of the Swift package manager. This category will accept email sent to: [email protected].
 
-**[LLBuild](http://forums.swift.org/c/development/llbuild)** - For developers to discuss the implementation of the low level build system (llbuild). This category will accept email sent to: [email protected]
+**[LLBuild](http://forums.swift.org/c/development/llbuild)** - For developers to discuss the implementation of the low level build system (llbuild). This category will accept email sent to: [email protected].
 
 **[Announcements](http://forums.swift.org/c/development/dev-announce)** - For announcements relevant to developers such as release announcements, branching, and infrastructure updates.
 
@@ -49,11 +49,11 @@ Please see the [Swift evolution repository](https://github.com/apple/swift-evolu
 
 **[Announcements](https://forums.swift.org/c/evolution/announce)** - For announcements of Swift evolution proposal reviews and results. All discussion and review of evolution proposals occurs on the swift-evolution mailing list.
 
-**[Pitches](https://forums.swift.org/c/evolution/pitches)** - For proposals for the evolution of Swift including new language features, new standard library APIs, and so on before they enter the review phase. This category will accept email sent to: [email protected]
+**[Pitches](https://forums.swift.org/c/evolution/pitches)** - For proposals for the evolution of Swift including new language features, new standard library APIs, and so on before they enter the review phase. This category will accept email sent to: [email protected].
 
-**[Proposal Reviews](https://forums.swift.org/c/evolution/proposal-reviews)** - Posting and commentary on proposals in the review phase. This category will accept email sent to: [email protected]
+**[Proposal Reviews](https://forums.swift.org/c/evolution/proposal-reviews)** - Posting and commentary on proposals in the review phase. This category will accept email sent to: [email protected].
 
-**[Discussion](https://forums.swift.org/c/evolution/discuss)** - For general discussion of the evolution of Swift. This category will accept email sent to: [email protected]
+**[Discussion](https://forums.swift.org/c/evolution/discuss)** - For general discussion of the evolution of Swift. This category will accept email sent to: [email protected].
 
 ### Server
 [Server]: #server

community/index.md

@@ -10,9 +10,9 @@ The Swift.org community has the singular goal of making the world's best general
 
 The Swift language is developed in the open, and all technical or administrative topics about the language or community processes should be directed to the Swift public forums. Public conversations are encouraged, and active developers of the Swift language should monitor the relevant forum categories.
 
-* Directory of forum categories and email instructions are in the [forum section](#forums)
-* Source code for all Swift projects can be found on GitHub at [github.com/apple][github]
-* The Swift language bug tracking system is maintained at [github.com/apple/swift/issues][bugtracker]
+* Directory of forum categories and email instructions are in the [forum section](#forums).
+* Source code for all Swift projects can be found on GitHub at [github.com/apple][github].
+* The Swift language bug tracking system is maintained at [github.com/apple/swift/issues][bugtracker].
 
 All communication within project spaces should adhere to Swift project's [Code of Conduct](/code-of-conduct).
 
@@ -22,16 +22,16 @@ Advancing the Swift programming language with a coherent, clear view of its evol
 
 
 * __[Project Lead](#project-lead)__ appoints technical leaders from the community.  Apple Inc. is the project lead, and interacts with the community through its representative.
-* __[Core Team](#core-team)__ is the small group responsible for strategic direction and oversight of the Swift project
-* __[Code Owner](#code-owners)__ is the individual responsible for a specific area of the Swift codebase
-* __[Committer](/contributing/#commit-access)__ is anyone that has commit access to the Swift code base
-* __[Contributor](/contributing/#contributing-code)__ is anyone that contributes a patch or helps with code review
+* __[Core Team](#core-team)__ is the small group responsible for strategic direction and oversight of the Swift project.
+* __[Code Owner](#code-owners)__ is the individual responsible for a specific area of the Swift codebase.
+* __[Committer](/contributing/#commit-access)__ is anyone that has commit access to the Swift code base.
+* __[Contributor](/contributing/#contributing-code)__ is anyone that contributes a patch or helps with code review.
 * __Workgroups__
-   * __[C++ Interoperability Workgroup](/cxx-interop-workgroup)__ is a team that works on adding the support for the bidirectional interoperability between Swift and C++
-   * __[Documentation Workgroup](/documentation-workgroup)__ is a steering team that helps guide the documentation experience for Swift
-   * __[Language Steering Group](#language-steering-group)__ is a small group of experts that drive the Swift language forward in a coherent direction
-   * __[Swift on Server Workgroup](/sswg)__ is a steering team that promotes the use of Swift for developing and deploying server applications
-   * __[Website Workgroup](/website-workgroup/)__ is a steering team that helps guide the evolution on the Swift.org website
+   * __[C++ Interoperability Workgroup](/cxx-interop-workgroup)__ is a team that works on adding the support for the bidirectional interoperability between Swift and C++.
+   * __[Documentation Workgroup](/documentation-workgroup)__ is a steering team that helps guide the documentation experience for Swift.
+   * __[Language Steering Group](#language-steering-group)__ is a small group of experts that drive the Swift language forward in a coherent direction.
+   * __[Swift on Server Workgroup](/sswg)__ is a steering team that promotes the use of Swift for developing and deploying server applications.
+   * __[Website Workgroup](/website-workgroup/)__ is a steering team that helps guide the evolution on the Swift.org website.
 
 Most importantly, everyone that uses Swift is a valued member of our extended community.
 

contributing/_contributing-code.md

@@ -150,12 +150,12 @@ People depend on Swift to create their production software.  This means that a b
 
 Additionally, the committer is responsible for addressing any problems found in the future that the change may cause. This responsibility means that you may need to update your change in order to:
 
-* Ensure the code compiles cleanly on all primary platforms
-* Fix any correctness regressions found in other test suites
-* Fix any major performance regressions
-* Fix any performance or correctness regressions in the downstream Swift tools
-* Fix any performance or correctness regressions that result in customer code that uses Swift
-* Address any bugs that appear in the bug tracker as a result from your change
+* Ensure the code compiles cleanly on all primary platforms.
+* Fix any correctness regressions found in other test suites.
+* Fix any major performance regressions.
+* Fix any performance or correctness regressions in the downstream Swift tools.
+* Fix any performance or correctness regressions that result in customer code that uses Swift.
+* Address any bugs that appear in the bug tracker as a result from your change.
 
 We prefer that these issues be handled before submission, but we understand that it isn’t possible to test all of this for every submission. Our continuous integration (CI) infrastructure normally finds these problems. We recommend watching the CI infrastructure throughout the next day to look for regressions. The CI infrastructure will directly email you if a group of commits that included yours caused a failure. You are expected to check those messages to see whether they are your fault and, if so, fix the breakage.
 

contributor-experience-workgroup/index.md

@@ -7,15 +7,15 @@ The Contributor Experience Workgroup supports contributors to the Swift project,
 
 ## Charter
 
-The Contributor Experience Workgroup is devoted to
-- improving the mechanics and ergonomics of contributing to the Swift compiler and related open source repositories by
-  - providing guidance and setting expectations for the GitHub pull request and issue workflows
-  - maintaining onboarding documentation
-  - adding and managing GitHub labels
-- providing support systems and facilitating collaboration amongst contributors through
-  - the Swift Mentorship Program
-  - community groups
-  - collaboration tools and spaces to connect with other contributors
+The Contributor Experience Workgroup is devoted to:
+- improving the mechanics and ergonomics of contributing to the Swift compiler and related open source repositories by:
+  - providing guidance and setting expectations for the GitHub pull request and issue workflows.
+  - maintaining onboarding documentation.
+  - adding and managing GitHub labels.
+- providing support systems and facilitating collaboration amongst contributors through:
+  - the Swift Mentorship Program.
+  - community groups.
+  - collaboration tools and spaces to connect with other contributors.
 
 ### Diversity
 

diversity/index.md

@@ -47,9 +47,9 @@ The Diversity in Swift workgroup will include posts on the Swift.org blog that r
 
 Everyone is welcome to participate in Diversity in Swift! Below are a few specific ways to contribute:
 
-* Joining community groups that you identify with
-* Proposing new community groups or programs
-* Sharing Swift content on the [Community Showcase](https://forums.swift.org/c/community-showcase)
-* Encouraging participation and highlighting work from developers who are currently underrepresented in the community
+* Joining community groups that you identify with.
+* Proposing new community groups or programs.
+* Sharing Swift content on the [Community Showcase](https://forums.swift.org/c/community-showcase).
+* Encouraging participation and highlighting work from developers who are currently underrepresented in the community.
 
 Anybody can work toward making the Swift community even more approachable. Members of the community can help newcomers overcome barriers by [answering questions on the Swift Forums](/contributing/#answering-questions), improving [open source Swift documentation](https://github.com/apple/swift/blob/main/docs/README.md), searching for or creating [good first issues](/contributing/#good-first-issues), and more.

documentation-workgroup/index.md

@@ -9,11 +9,11 @@ documentation experience for Swift.
 The Documentation Workgroup will:
 
 * Define and prioritize efforts that address the documentation needs of the
-  Swift community
-* Actively guide development for documentation tooling such as Swift-DocC
+  Swift community.
+* Actively guide development for documentation tooling such as Swift-DocC.
 * Define processes that govern contributions to Swift’s documentation
-  experience
-* Channel feedback to Swift Core Team about the needs of the Swift community
+  experience.
+* Channel feedback to Swift Core Team about the needs of the Swift community.
 
 The current Documentation Workgroup consists of the following people:
 
@@ -67,10 +67,10 @@ The Core Team also selects one member of the workgroup as the chair. The chair
 has no special authority over the workgroup, but they are responsible for
 ensuring its smooth functioning, including by:
 
-* Organizing and leading regular meetings
-* Ensuring that the workgroup communicates effectively with the community
+* Organizing and leading regular meetings.
+* Ensuring that the workgroup communicates effectively with the community.
 * Coordinating meetings between workgroup representatives and the Core Team
-  when issues need to be raised to the Core Team
+  when issues need to be raised to the Core Team.
 
 Workgroup members will try to make a decision independently by consensus
 whenever possible, and will raise issues to the Core Team when there are particular
@@ -90,11 +90,11 @@ experience and the Documentation Workgroup’s initiatives. If you’d like to
 contribute, consider:
 
 * Joining the Documentation Workgroup’s open meetings on WebEx (reach out to
-    `@swift-documentation-workgroup` in forums for details)
+    `@swift-documentation-workgroup` in forums for details).
 * Discussing ideas in the Swift Forums, for example in the [Swift-DocC
   forum](https://forums.swift.org/c/development/swift-docc) for
-  Swift-DocC–related ideas
+  Swift-DocC–related ideas.
 * Opening issues to track enhancements and bugs for the projects governed by the Documentation Workgroup:
-  [Swift-DocC](https://github.com/apple/swift-docc/issues), [The Swift Programming Language book](https://github.com/apple/swift-book/issues)
+  [Swift-DocC](https://github.com/apple/swift-docc/issues), [The Swift Programming Language book](https://github.com/apple/swift-book/issues).
 * Participating in the [Swift Mentorship
-  Program](/mentorship)
+  Program](/mentorship).