diff --git a/Documentation/Appendix/SettingUpTypo3Ddev.rst b/Documentation/Appendix/SettingUpTypo3Ddev.rst index 9a56120..fadd5d1 100644 --- a/Documentation/Appendix/SettingUpTypo3Ddev.rst +++ b/Documentation/Appendix/SettingUpTypo3Ddev.rst @@ -266,7 +266,7 @@ Resources Remember, you can use the Slack channels to ask for help! Follow the general convention for the channels: not too chatty, get straight to the point and ask, be nice. Register for -the `TYPO3 slack workspace `__ if you have not +the `TYPO3 slack workspace `__ if you have not done so already. .. _ddev-next-resources-slack: diff --git a/Documentation/Appendix/Slack.rst b/Documentation/Appendix/Slack.rst index 5bd3a3b..d9642c9 100644 --- a/Documentation/Appendix/Slack.rst +++ b/Documentation/Appendix/Slack.rst @@ -28,5 +28,5 @@ You do not need to ask for permission when asking a question. Ask your question in the channel and wait for a response. -As always, make sure to follow the `Code of conduct `__ +As always, make sure to follow the `Code of conduct `__ or the short form: **be nice, be helpful!** diff --git a/Documentation/Appendix/Windows/CloneWithSourcetree.rst b/Documentation/Appendix/Windows/CloneWithSourcetree.rst index 5dd8a92..3540172 100644 --- a/Documentation/Appendix/Windows/CloneWithSourcetree.rst +++ b/Documentation/Appendix/Windows/CloneWithSourcetree.rst @@ -128,7 +128,7 @@ following command to the bash and execute it: .. code-block:: bash - curl -o .git/hooks/commit-msg "https://typo3.org/fileadmin/resources/git/commit-msg.txt" && chmod +x .git/hooks/commit-msg + cp Build/git-hooks/commit-msg .git/hooks/commit-msg && chmod +x .git/hooks/commit-msg .. note:: diff --git a/Documentation/HandlingAPatch/Tips.rst b/Documentation/HandlingAPatch/Tips.rst index ad50b69..7bb8c06 100644 --- a/Documentation/HandlingAPatch/Tips.rst +++ b/Documentation/HandlingAPatch/Tips.rst @@ -114,8 +114,8 @@ This is what you can do: * Act helpful and friendly: Chances are higher that your patch will be merged if the way you are communicating is fair. This is even more important for reviewers and active contributors, we do not allow ranters and haters in our - team and we try to stick to our - `Code of conduct `__ + team and we try to stick to our + `Code of conduct `__. Please keep that in mind when working with us. You will be rewarded with the pleasure of working with a group of pretty smart people if you act accordingly. diff --git a/Documentation/HandlingIssues/TicketWorkflow.rst b/Documentation/HandlingIssues/TicketWorkflow.rst index 174942f..174540f 100644 --- a/Documentation/HandlingIssues/TicketWorkflow.rst +++ b/Documentation/HandlingIssues/TicketWorkflow.rst @@ -82,8 +82,7 @@ Status Please bear in mind that this status does not mean someone immediately begins to work on it. It is just a status that developers can use to search for accepted issues to work on. And it is a good pool of issues - to address for example in remote or on-site Code sprints (see - `https://typo3.org/community/meet/regular-open-sprints`__). + to address for example in remote or on-site Code sprints. #. In Progress diff --git a/Documentation/ReportingAnIssue/Index.rst b/Documentation/ReportingAnIssue/Index.rst index 782f4b9..816fbcd 100644 --- a/Documentation/ReportingAnIssue/Index.rst +++ b/Documentation/ReportingAnIssue/Index.rst @@ -104,7 +104,7 @@ Talk to the core team bug or feature) yourself, but need some guidance on how to approach it, don't hesitate to talk to us on `Slack `__ in the **#typo3-cms-coredev** - channel. (Remember to `register `__ + channel. (Remember to `register `__ first.) This channel is not a support channel for end-users. Those needs are covered by `https://typo3.org/help`__.