symfony
diff --git a/‎console.rst
Copy file name to clipboardExpand all lines: console.rst
+1-1Lines changed: 1 addition & 1 deletion b/‎console.rst
Copy file name to clipboardExpand all lines: console.rst
+1-1Lines changed: 1 addition & 1 deletion
diff --git a/‎contributing/code/core_team.rst
Copy file name to clipboardExpand all lines: contributing/code/core_team.rst
+1-4Lines changed: 1 addition & 4 deletions b/‎contributing/code/core_team.rst
Copy file name to clipboardExpand all lines: contributing/code/core_team.rst
+1-4Lines changed: 1 addition & 4 deletions
diff --git a/‎form/multiple_buttons.rst
Copy file name to clipboardExpand all lines: form/multiple_buttons.rst
+2-2Lines changed: 2 additions & 2 deletions b/‎form/multiple_buttons.rst
Copy file name to clipboardExpand all lines: form/multiple_buttons.rst
+2-2Lines changed: 2 additions & 2 deletions
diff --git a/‎form/unit_testing.rst
Copy file name to clipboardExpand all lines: form/unit_testing.rst
+3-3Lines changed: 3 additions & 3 deletions b/‎form/unit_testing.rst
Copy file name to clipboardExpand all lines: form/unit_testing.rst
+3-3Lines changed: 3 additions & 3 deletions
@@ -449,7 +449,7 @@ call ``setAutoExit(false)`` on it to get the command result in ``CommandTester``
 .. note::
 
     When using the Console component in a standalone project, use
-    :class:`Symfony\\Component\\Console\\Application <Symfony\\Component\\Console\\Application>`
+    :class:`Symfony\\Component\\Console\\Application`
     and extend the normal ``\PHPUnit\Framework\TestCase``.
 
 Logging Command Errors
 
@@ -111,7 +111,7 @@ Symfony contributions:
 Core Membership Application
 ~~~~~~~~~~~~~~~~~~~~~~~~~~~
 
-At present, new Symfony Core membership applications are not accepted.
+About once a year, the core team discuss the opportunity to invite new members.
 
 Core Membership Revocation
 ~~~~~~~~~~~~~~~~~~~~~~~~~~
@@ -123,9 +123,6 @@ A Symfony Core membership can be revoked for any of the following reasons:
 * Willful negligence or intent to harm the Symfony project;
 * Upon decision of the **Project Leader**.
 
-Should new Symfony Core memberships be accepted in the future, revoked
-members must wait at least 12 months before re-applying.
-
 Code Development Rules
 ----------------------
 
 
@@ -6,7 +6,7 @@ How to Submit a Form with Multiple Buttons
 
 When your form contains more than one submit button, you will want to check
 which of the buttons was clicked to adapt the program flow in your controller.
-To do this, add a second button with the caption "Save and add" to your form::
+To do this, add a second button with the caption "Save and Add" to your form::
 
     $form = $this->createFormBuilder($task)
         ->add('task', TextType::class)
@@ -17,7 +17,7 @@ To do this, add a second button with the caption "Save and add" to your form::
 
 In your controller, use the button's
 :method:`Symfony\\Component\\Form\\ClickableInterface::isClicked` method for
-querying if the "Save and add" button was clicked::
+querying if the "Save and Add" button was clicked::
 
     if ($form->isSubmitted() && $form->isValid()) {
         // ... perform some action, such as saving the task to the database
 
@@ -55,7 +55,7 @@ The simplest ``TypeTestCase`` implementation looks like the following::
             ];
 
             $model = new TestObject();
-            // $formData will retrieve data from the form submission; pass it as the second argument
+            // $model will retrieve data from the form submission; pass it as the second argument
             $form = $this->factory->create(TestedType::class, $model);
 
             $expected = new TestObject();
@@ -67,7 +67,7 @@ The simplest ``TypeTestCase`` implementation looks like the following::
             // This check ensures there are no transformation failures
             $this->assertTrue($form->isSynchronized());
 
-            // check that $formData was modified as expected when the form was submitted
+            // check that $model was modified as expected when the form was submitted
             $this->assertEquals($expected, $model);
         }
 
@@ -88,7 +88,7 @@ The simplest ``TypeTestCase`` implementation looks like the following::
 So, what does it test? Here comes a detailed explanation.
 
 First you verify if the ``FormType`` compiles. This includes basic class
-inheritance, the ``buildForm()`` function and options resolution. This should
+inheritance, the ``buildForm()`` method and options resolution. This should
 be the first test you write::
 
     $form = $this->factory->create(TestedType::class, $formData);