feat(technical-file): semantically separate technical file from project reports

subjects/devops/technical-file/README.md

@@ -2,27 +2,27 @@
 
 ### Objective
 
-To prepare to compile a technical file, with a view to obtaining the Level 7 RNCP title of Cloud DevOps expert.
+To prepare to compile a technical file, with a view to obtaining the Level 7 RNCP title of Cloud DevOps Expert.
 
-You'll write a project report for each project you validate during your training, so that you can trace your achievements. You'll use your reports to compile a **personal** technical file at the end of your study period.
+At the end of your training period, you'll have 5 days to compile your **personal** technical file.
 
-### Preparing for your technical file
+During your training, each time you validate a project, you will write a project report.
 
-Each time you validate a project (whether alone or in a group), you'll need to write a report. This must be completed individually, so that is shows **your** understanding.
+You will use your project reports to trace your achievements, to enable you to compile your technical file.
 
-The focus of your technical file is to detail what you have learned, and what you have achieved during your training. This allows you to demonstrate your mastery of:
+### Writing your project reports
 
-- Knowledge of Cloud Service Providers and Infrastructure
+Each time you validate a project (whether alone or in a group), you'll need to write a project report.
-- Automation and orchestration of containerized services
-- DevOps project management
 
-You should write and store your reports inside the repository of this project. The repository will be comprised of a series of markdown files, with one for each project that you validate during your training. These should be named as `project-name.md`, so that you can trace your progress.
+The objective is to enable you to trace your achievements, so that you can compile your technical file at the end of your training period.
 
-You will have 5 additional days beyond the end of your training to finalize your technical file.
+Your technical file will be comprised of three core areas. You'll need to document enough information to cover the core skill blocks:
 
-### Contents of the reports
+- Knowledge of Cloud Service Providers and Infrastructure
+- Automation and orchestration of containerized services
+- DevOps project management
 
-The reports must detail a description of the project, and justifications for your choices. You should cover:
+To enable you to do this, your reports should detail:
 
 - The problem you needed to solve
 - The constraints you needed to work with
@@ -31,12 +31,16 @@ The reports must detail a description of the project, and justifications for you
   - Continuous delivery
   - Quality control
 - The technological choices you made
-- The expected results, and anticipated problems
+- The expected results, and actual results
-- The obtained results, and actual problems faced
+- The expected problems, and actual problems faced
+
+You should store your project reports inside the repository of this project. The result will be a series of Markdown files, with one for each project that you validate during your training.
+
+Your project reports should be named `project-name.md`, so that you can more easily trace your achievements to compile your technical file later.
 
 ### Compiling the technical file
 
-You will have 5 days after the end of your training period in which to finalize your technical file.
+You will have 5 days after the end of your training period in which to compile your technical file.
 
 Your technical files must be an individual piece of work, and be comprised of approximately 8-10 pages.
 
@@ -44,34 +48,27 @@ You will rely on the contents of your project reports in order to trace your ach
 
 Particular care must be given to spelling and presentation.
 
-### Technical files contents
+Your technical file must demonstrate your knowledge in the following core skill blocks:
-
-Your technical file must demonstrate your knowledge in the following skill blocks:
 
 - **Knowledge of cloud infrastructure**
   - Understand and configure security services
   - Be responsible for the choice of hyperscalers
-  - Set up observability systems on the perimeter of infrastructures and
+  - Set up observability systems on the perimeter of infrastructures and apps
-apps
+  - Manage authentication, cookies and sessions
-  - Manage authentication, cookies, sessions
   - Build, manage and run applications in isolated/containerized environments
   - Install and manage Linux servers
   - Use relational and non-relational databases
 - **Automation, management and orchestration of containerized services**
-  - Automate and orchestrate the different stages of continuous integration pipelines
+  - Automate and orchestrate the different stages of continuous integration pipelines and continuous delivery (CI/CD) in a smooth and easily repeatable way
-and Continuous Deployment (CI/CD) in a smooth and easily repeatable way
   - Automate configuration tasks
   - Automate and orchestrate server management
   - Automate test procedures
-  - Automate the development of the integration chain deployment steps
+  - Automate the development of the integration chain deployment steps and continuous delivery
-and continuous deployment
 - **DevOps project management and management**
   - Exploit the expression of need of the product team
-  - Be responsible for the collection and analysis of performance data from the
+  - Be responsible for the collection and analysis of performance data from the integration and deployment phases
-integration and deployment phases
+  - Be responsible for the reliability, clarity, traceability and security of the code and deliverables
-  - Be responsible for the reliability, clarity, traceability and security of the code and
-deliverables
   - Be responsible for managing code versioning
-  - Implement security practices for applications and services
+  - Implement security practices for applications and services deployed in the cloud
-deployed in the cloud
   - Be responsible for sharing knowledge and disseminating good Agile DevOps practices
+