Updated titles font size

docs/timeline/team-meetings.md

@@ -10,46 +10,46 @@ parent: Timeline
 This section describes a summarized record of information, decisions, and actions made during the develop meetings.
 {: .fs-6 .fw-300 }
 
-## 05/03/2023
+### 05/03/2023
 - Created a WhatsApp group to establish communication within the team;
 - Conducted team introductions and shared knowledge among team members;
 - Formulated a plan to complete the required FIAP classes before initiating project development;
 - Established a Kanban board to effectively track project progress;
 - Unanimously agreed to conduct the entire project in English (en-US).
 
-## 05/10/2023
+### 05/10/2023
 - Organized a group session to watch YouTube live sessions by Professor Nélio Alves (DevSuperior) to acquire additional knowledge and insights.
 
-## 05/17/2023
+### 05/17/2023
 - Developed a Minimum Viable Product (MVP) based on Professor Nélio Alves' project;
 - Deployed the application on Amazon Web Services (AWS) using EC2 for compute resources and RDS for the database.
 
-## 05/25/2023
+### 05/25/2023
 - Successfully completed all available classes on the FIAP ON platform;
 - Decided to schedule team meetings on Tuesdays and Thursdays at 9 PM for enhanced flexibility;
 - Deployed the application on the Railway platform to validate its functionality using two containers.
 
-## 05/30/2023
+### 05/30/2023
 - Utilized the Live Share extension in Visual Studio Code for collaborative group programming on the application.
 
-## 06/01/2023
+### 06/01/2023
 - Resolved bugs and implemented additional validations for the User API;
 - Eliminated stack trace information from error responses (500);
 - Created recursive user relationship;
 - Developed a spreadsheet to simulate data modeling and facilitate the creation of SQL scripts for the Microsoft SQL Server database to validate the solution;
 - Increased the number of records in the database seeding file for the "users" and "user_relations" tables.
 
-## 06/06/2023
+### 06/06/2023
 - Hernandes Andrade voluntarily left the team;
 - Individual developments were analysed by the members through Code Review, using GitHub's resources;
 - Created the Address API and expanded the database seeding file for the "addresses" and "address_relation" tables;
 - Locked the main branch to enforce code pushes through pull requests, allowing evaluation by code owners.
 
-## 06/14/2023
+### 06/14/2023
 - Created data records for the "appliances" and "appliance_relations" through database seeding file;
 - We decided to use the Mintlify Doc Writer plugin to generate documentation following the Javadoc pattern.
 
-## 06/20/2023
+### 06/20/2023
 - Several code changes were made based on the insights gained from the "Coda Comigo" lives;
 - Refactored service classes to return only the entity, leaving the ResponseEntity for the Controller;
 - Converted the ID of entities from Long to UUID, along with updating all related dependencies;
@@ -59,30 +59,31 @@ This section describes a summarized record of information, decisions, and action
 - Initiated documentation by adding initial comments to classes using the Mintlify Doc Writer plugin;
 - Changed the data type of timestamps from DateTime to Instant.
 
-## 06/22/2023
+### 06/22/2023
 - Utilized Google Docs to document ideas and discussions;
 - Refactored the documentation generated by the Mintlify Doc Writer;
 - Introduced the beecrowd.com platform for algorithm training and improving programming logic skills.
 
-## 06/27/2023
+### 06/27/2023
 - Incorporated the springdoc-openapi-ui framework to generate interactive and navigable API documentation;
 - Utilized Postman to support the development of interactive documentation.
 
-## 06/30/2023
+### 06/30/2023
 - Utilized the just-the-docs template to structure the wiki;
 - Created the main page of the project and provided detailed descriptions for each section;
 - Designed and incorporated a project logo on wiki pages;
 - Finalized the base structure of the wiki.
 
-## 07/02/2023
+### 07/02/2023
 - Added Javadocs into GitHub repository for a more comprehensive documentation;
 - Included request examples in Swagger for improving the API documentation;
 - Configured CORS settings to enable requests from Swagger UI to the API;
 - Successfully deployed the solution on Railway;
 - Defined detailed documentation for the User, Address, and Appliance entities in the wiki;
 - Updated the Swagger API to use HTTPS on request URLs; 
+- Used GitHub HTML Preview to visualize the Javadoc pages; 
 - Updated the README.md file with links to Swagger API docs, project wiki, and Javadocs.
 
-## 07/03/2023
+### 07/03/2023
 - Described the "timeline" wiki section;
 - Create a PDF file to contains all required challenge links.