Merge pull request #61 from rust-lang-ua/SupperZum-patch-2

add headers to faq.md

faq.md

@@ -8,110 +8,110 @@
 
 ## About Rustcamp
 
-<ins>*- What is the motivation of mentors to mentor?*</ins><br/>
+##### <ins>*- What is the motivation of mentors to mentor?*</ins><br/>
 
 All our mentors are professionals, many of whom own their companies and are in a position to hire talented participants. Mentoring not only improves their knowledge but also satisfies their innate desire to help others.
 
-<ins>*- Do we cooperate with IT companies in any way?*</ins><br/>
+##### <ins>*- Do we cooperate with IT companies in any way?*</ins><br/>
 
 We are making a lot of efforts to involve companies in interviews with rustcamp graduates and hopefully we will get there. We currently have 4 partner companies: TacansLab, AI Edge Lab, Intellias, and Near.
 
-<ins>*- Can I only complete the course assignments on weekends?*</ins><br/>
+##### <ins>*- Can I only complete the course assignments on weekends?*</ins><br/>
 
 To achieve quality results, you should dedicate more than 20 hours a week to your studies. Three months of intensive study can equate to two years of independent practice. If you only study on weekends, you'd need to dedicate 10 hours each day. We recommend distributing your study time evenly throughout the week.
 
 
 ## Communication
 
-<ins>*- Where can I ask for help?*</ins><br/>
+##### <ins>*- Where can I ask for help?*</ins><br/>
 
 Firstly, ask your peers in the Rustcamp's chat. You can also post your questions in the Telegram [chat of our community](https://t.me/rustlang_ua), the official [forum](https://users.rust-lang.org/). [ChatGPT](https://openai.com/blog/chatgpt) works well for simpler queries. However, remember that your solutions must be original, and anyone found sharing or copying solutions will be expelled.
 
-<ins>*- What is the best way to ask questions?*</ins><br/>
+##### <ins>*- What is the best way to ask questions?*</ins><br/>
 
 It's preferable to have your code in the [playground](https://play.rust-lang.org/). This way, mentors and peers don't have to spend extra time recreating the problem.
 
 ![playground_ask](https://github.com/rust-lang-ua/rustcamp/assets/98274821/2351bddd-455f-4078-a7cb-328a7bb08ac9)
 
-<ins>*- Is the Telegram chat moderated?*</ins><br/>
+##### <ins>*- Is the Telegram chat moderated?*</ins><br/>
 
 Initially, we won't restrict communication in the chat or divide it into sub-chats. We encourage participants to get to know each other. However, we may implement stricter moderation rules later if needed. For now, respect all chat participants and refrain from offensive behavior.
 
-<ins>*- When and how are the meetings conducted?*</ins><br/>
+##### <ins>*- When and how are the meetings conducted?*</ins><br/>
 
 Meetings are held four times a week on weekdays (except Tuesday) according to your group's schedule. The meeting lasts about 1 hour. All appointments will be in your calendar. Attendance at the first meeting is mandatory.
 
-<ins>*- Will the meetings be recorded?*</ins><br/>
+##### <ins>*- Will the meetings be recorded?*</ins><br/>
 
 No, we usually don't record meetings. So, ensure you don't miss them.
 
-<ins>*- What should I do if my contact information has changed?*</ins><br/>
+##### <ins>*- What should I do if my contact information has changed?*</ins><br/>
 
 If you change your GitHub username, email, or telegram, be sure to let [Stepan](https://t.me/stepko_o) know.
 
 ## Completing tasks and PR
 
-<ins>*- What is PR?*</ins><br/>
+##### <ins>*- What is PR?*</ins><br/>
 
 PR is an abbreviation for [Pull Request](https://docs.github.com/en/pull-requests/collaborating-with-pull-requests/proposing-changes-to-your-work-with-pull-requests/about-pull-requests).
 
-<ins>*- How should I name PR?*</ins><br/>
+##### <ins>*- How should I name PR?*</ins><br/>
 
 Each task should be submitted as a separate PR on its own branch. Use the following template for the PR name: `task_task_number`. Here are some examples:
 
 - "task_0" for the task in the zero section,
 - "task_1_3" for the third task in the first section,
 - "task_5_3_11" for the 11th subtask of the third task in the fifth section,
 
-<ins>*- What is the final task?*</ins><br/>
+##### <ins>*- What is the final task?*</ins><br/>
 This is the last task of the section, namely:
 - Task_1_10 : 1_concepts/README.md
 - Task_2_7 : 2_idioms/README.md 
 - Task_3_12 : 3_ecosystem/README.md 
 - Task_4_4 : 4_backend/README.md
 Questions should be answered in writing only in them.
 
-<ins>*- Should I answer theoretical questions in PR?*</ins><br/>
+##### <ins>*- Should I answer theoretical questions in PR?*</ins><br/>
 Only in the [final tasks](https://github.com/rust-lang-ua/rustcamp/edit/master/faq.md#--what-is-the-final-task).
 In tasks that are not final, you do not need to answer theoretical questions. For example, in Problems 1_1, 1_2, you do not need to answer the theoretical questions in writing because they are not final.
 In the final tasks, please write your answers in the same PR as the solution to the practical problem. Do not create a separate PR to answer the questions; it will not be accepted by mentors.
 
-<ins>*- How do I start completing tasks?*</ins><br/>
+##### <ins>*- How do I start completing tasks?*</ins><br/>
 
 [Our bot](https://github.com/1tbot) will create a private fork of the main [Rustcamp repository](https://github.com/rust-lang-ua/rustcamp) in [our organization](https://github.com/rust-lang-ua) and invite you. For more information on how to configure the received repository, see the [instructions](https://github.com/rust-lang-ua/rustcamp/blob/master/orientation.md#getting-started). Don't forget to tag all of your mentors in the comments section of the PR.
 
-<ins>*- How and where do I send Pull Requests of completed tasks?*</ins><br/>
+##### <ins>*- How and where do I send Pull Requests of completed tasks?*</ins><br/>
 
 Create a separate branch for each task in your private fork. Complete the task in the corresponding branch and create a PR to your main master branch. Don't forget to tag all of your mentors in the comments section of the PR.
 
-<ins>*- When is a task considered completed?*</ins><br/>
+##### <ins>*- When is a task considered completed?*</ins><br/>
 
 A task is marked as completed when you've made a Pull Request, and it's been reviewed, approved and merged. After you complete your Pull Request, remove the "NOT READY / DRAFT / WIP" marker from the title and specify [our bot](https://github.com/1tbot) as a reviewer and tag all of your mentors in the comments section. Before mentor can merge your pull request into the main branch, you need to receive approval. If more than one mentor has reviewed your Pull Request and requested changes, you must receive approval from all involved mentors. If all the conditions are executed, mentors will be able to merge your PR and task considered as completed.
 
-<ins>*- How do mentors distinguish between finished Pull Requesters and unfinished Pull Requesters?*</ins><br/>
+##### <ins>*- How do mentors distinguish between finished Pull Requesters and unfinished Pull Requesters?*</ins><br/>
 
 A task is marked as completed when you've made a Pull Request, and it's been reviewed and approved by one of the reviewers. After you complete your Pull Request, remove the "NOT READY / DRAFT / WIP" marker from the title and specify [our bot](https://github.com/1tbot) as a reviewer and tag all of your mentors in the comments section.
-<ins>*- Should I open an unfinished PR?*</ins><br/>
+##### <ins>*- Should I open an unfinished PR?*</ins><br/>
 
 Yes, you should. Open a PR as soon as you can, marking it with "NOT READY / DRAFT / WIP" in the title . Your mentors will review it once you remove this marker and specify [our bot](https://github.com/1tbot) as a reviewer and tag all of your mentors in the comments section.
 
-<ins>*- Can I merge PR?*</ins><br/>
+##### <ins>*- Can I merge PR?*</ins><br/>
 
 Please don't do PR merge yourself. Your mentors make the merge themselves. 
 
-<ins>*- How many mentors need to approve before I can merge?*</ins><br/>
+##### <ins>*- How many mentors need to approve before I can merge?*</ins><br/>
 
 You need approval from at least one mentor before merging the Pull Request into the main branch. However, if more than one mentor has reviewed your Pull Request and requested changes, you must receive approval from all of them.
 
-<ins>*- Where should I answer the questions in the first chapter?*</ins><br/>
+##### <ins>*- Where should I answer the questions in the first chapter?*</ins><br/>
 
 You can provide the answers under each question by editing your own md-file.
 
-<ins>*- What should I do if I find mistakes in the repository?*</ins><br/>
+##### <ins>*- What should I do if I find mistakes in the repository?*</ins><br/>
 
 We encourage you to open an __issue__ if you see any problems.
 
-<ins>*- How can I incorporate changes from the main repository?*</ins><br/>
+##### <ins>*- How can I incorporate changes from the main repository?*</ins><br/>
 
 Most likely, you won't need to merge upstream because [our bot](https://github.com/1tbot) will do it automatically. But in case you need to manually merge upstream, here are the instructions:
 
@@ -132,7 +132,7 @@ git merge upstream/master
 > This might happen if the repository is modified in some way before it is synced with the template.
 > If the changes are not significant, it is probably easier to try again from the start. Otherwise, here is one way to fix such an issue:
 
-<ins>*- What to do if you merged with `--allow-unrelated-histories`, but there are too many merge conflicts?*</ins><br/>
+##### <ins>*- What to do if you merged with `--allow-unrelated-histories`, but there are too many merge conflicts?*</ins><br/>
 
 1. You need to restore the state of your repository before the unsuccessful merge.
 
@@ -209,7 +209,7 @@ git push
 
 ## Capstone project
 
-<ins>*- I can't choose my capstone project. Can you suggest some?*</ins><br/>
+##### <ins>*- I can't choose my capstone project. Can you suggest some?*</ins><br/>
 
 <details>
 <summary>Gamepad Tester and Mapper</summary>