8000 minor #9622 Be consistent how we write "core team" (Nyholm) · symfony/symfony-docs@c02348e · GitHub
[go: up one dir, main page]

Skip to content

Commit c02348e

Browse files
committed
minor #9622 Be consistent how we write "core team" (Nyholm)
This PR was submitted for the master branch but it was merged into the 2.7 branch instead (closes #9622). Discussion ---------- Be consistent how we write "core team" While writing another PR, I discovered that we are not consistent how we refer to the Symfony core team. We are currently using "core team", "Core team", "Core Team" and "core-team". This PR make sure that we are always using "core team". That term was the most popular one. Commits ------- 4473a23 Be consistent how we write "core team"
2 parents b946e78 + 4473a23 commit c02348e

File tree

2 files changed

+4
-4
lines changed

2 files changed

+4
-4
lines changed

contributing/code/core_team.rst

Lines changed: 2 additions & 2 deletions
Original file line numberDiff line numberDiff line change
@@ -9,7 +9,7 @@ All the Symfony Core members are long-time contributors with solid technical
99
expertise and they have demonstrated a strong commitment to drive the project
1010
forward.
1111

12-
This document states the rules that govern the Symfony Core team. These rules
12+
This document states the rules that govern the Symfony core team. These rules
1313
are effective upon publication of this document and all Symfony Core members
1414
must adhere to said rules and protocol.
1515

@@ -121,7 +121,7 @@ Active Core Members
121121
Former Core Members
122122
~~~~~~~~~~~~~~~~~~~
123123

124-
They are no longer part of the Core Team, but we are very grateful for all their
124+
They are no longer part of the core team, but we are very grateful for all their
125125
Symfony contributions:
126126

127127
* **Bernhard Schussek** (`webmozart`_);

contributing/code/security.rst

Lines changed: 2 additions & 2 deletions
Original file line numberDiff line numberDiff line change
@@ -11,13 +11,13 @@ Reporting a Security Issue
1111
If you think that you have found a security issue in Symfony, don't use the
1212
bug tracker and don't publish it publicly. Instead, all security issues must
1313
be sent to **security [at] symfony.com**. Emails sent to this address are
14-
forwarded to the Symfony core-team private mailing-list.
14+
forwarded to the Symfony core team private mailing-list.
1515

1616
Resolving Process
1717
-----------------
1818

1919
For each report, we first try to confirm the vulnerability. When it is
20-
confirmed, the core-team works on a solution following these steps:
20+
confirmed, the core team works on a solution following these steps:
2121

2222
#. Send an acknowledgement to the reporter;
2323
#. Work on a patch;

0 commit comments

Comments
 (0)
0