Added point to expected behaviour, altered indexing

[AoifeHughes]

Summary

This pull request adds a new bullet point to the "2.1 Expected Behaviour" section of the Code of Conduct, encouraging open and inclusive conversations and discouraging the use of direct messaging (DMs) for project-related topics. It also has rearranged the indexing of the headings such that everything is under the primary one.

List of changes proposed in this PR (pull-request)

• Add a new bullet point under the "2.1 Expected Behaviour" section to promote open and inclusive conversations and discourage the use of DMs for project-related discussions.

What should a reviewer concentrate their feedback on?

• Does the new bullet point align with the overall tone and style of the Code of Conduct?
• Is the wording of the new bullet point clear and easy to understand?
• Are there any other areas in the Code of Conduct where this change should be reflected?

Acknowledging contributors

• All contributors to this pull request are already named in the table of contributors in the README file.

• The following people should be added to the table of contributors in the README file: @AoifeHughes

[welcome]

💖 Thanks for opening this pull request! 💖 The Turing Way community really appreciates your time and effort to contribute to the project. Please make sure you have read our Contributing Guidelines and filled in our pull request template to the best of your ability.
If you are submitting a new chapter, here are some things that will help get your pull request across the finish line! 🏁

• Check you have removed all lorem ipsums from the chapter template (if you used it)
• Check for any abbreviations or latin phrases (such as "e.g." or "i.e.") in your writing. See our style guide for more information on this topic.
• Make sure you have added your new chapter to the Table of Contents
  
  We have Continuous Integration tests that check the writing style and will help you track down any slip-ups ♻ The Netlify bot will also comment with a preview of the book with your additions so you can see how it will look once it's merged! 🎉
  
  We get a lot of pull requests on this repo, so please be patient and we will get back to you as soon as we can. If we don't acknowledge this pull request after 7 days, feel free to chat to us about it in our Slack workspace.

[netlify]

✅ Deploy Preview for the-turing-way ready!

Name	Link
🔨 Latest commit	cb6ca40
🔍 Latest deploy log	https://app.netlify.com/sites/the-turing-way/deploys/6641ce08984877000960fe42
😎 Deploy Preview	https://deploy-preview-3643--the-turing-way.netlify.app
📱 Preview on mobile	Toggle QR Code... Use your smartphone camera to open QR code link.

---

To edit notification comments on pull requests, go to your Netlify site configuration.

[da5nsy]

I think this is a valuable and appropriate addition, which is well-phrased.

The formatting fixes also get a big thumbs up from me 👍

[da5nsy]

Are there any other areas in the Code of Conduct where this change should be reflected?

I don't this so

[JimMadge]

Just noting that there are PRs to put the CoC (with some changes proposed) here so that it will be inherited by all repos on the org.

[AoifeHughes]

Notes from co-working meeting today:

• There's a lack of form of how to raise concerns @AlexandraAAJ
  • This already exists and needs added https://forms.office.com/Pages/ResponsePage.aspx?id=p_SVQ1XklU-Knx-672OE-Y7Akle7QvZEgPbWyXh31R9URUpDS041TkZVVDZPQkM1N1RVWUg4MUlBUi4u

[AoifeHughes]

Also how do we give feedback of changing made in response to raising conduct (or other) issues

[AoifeHughes]

• Are committee members up-to-date https://github.com/the-turing-way/the-turing-way/blob/main/CODE_OF_CONDUCT.md#contact-for-reporting
• Can we also stress when someone is non-Turing in case someone feels that Turing isn't a safe space for problems to be raised (the email addresses, not the people I mean)

[AoifeHughes]

• Think about how the code of conduct relates to translations in other languages of the repo and if it should be made available (and if we have the scope/resources to do so)
  • Reach out to the translation team on slack