Fix tense

_posts/2024-08-20-js-nation-react-summit-2024.md

@@ -19,7 +19,7 @@ The Frontend Bedrock teams were present at the 2024 edition of the _JS Nation_ a
 
 One of my favourite types of presentation, with concrete things that you can then apply in your daily life as a developer.
 
-Alex summed up his speech in 5 points:
+Alex sums up his speech in 5 points:
 
 - **Accept imperfections** in your codebase: perfect is the ennemy of good, shortcuts and exceptions can be taken if they are well documented.
 - **[Colocate code](https://alexmoldovan.dev/code-bites/colocation-is-king)** according to concerns is a way of improving readability and therefore maintainability and efficiency.
@@ -33,7 +33,7 @@ At Bedrock, we've always tried to apply a maximum of [best practices](https://te
 
 > 📹 Watch the [video](https://gitnation.com/contents/why-your-performance-work-is-not-seen)
 
-Vinicius addressed an important subject for us, as frontend engineers. We all are concerned about performance and we want to deliver the most optimized product, but we often come up against major obstacles in this area. We already talked about this topic last year when [we attended the We Love Speed conference](https://tech.bedrockstreaming.com/2023/08/11/we-love-speed-2023.html).
+Vinicius addresses an important subject for us, as frontend engineers. We all are concerned about performance and we want to deliver the most optimized product, but we often come up against major obstacles in this area. We already talked about this topic last year when [we attended the We Love Speed conference](https://tech.bedrockstreaming.com/2023/08/11/we-love-speed-2023.html).
 
 To prove values of performance work, **Lab tools** (like [Lighthouse](https://developer.chrome.com/docs/lighthouse/overview?hl=fr)) & **RUM** (Real User Monitoring) has to been used together. Data collected must be analysed, optimised and framed to make connections with product concerns. Performance needs to **matter to engineering and product** for a sustainable governance model.
 
@@ -43,9 +43,9 @@ As in many areas, the key is to set realistic and achievable objectives and to p
 
 > 📹 Watch the [video](https://gitnation.com/contents/install-nothing-app-uis-with-native-browser-apis)
 
-Scott revealed that we can use the browser's native APIs to build certain UI components easily, whereas we've been using sometimes complex JS to do this for years.
+Scott reveals that we can use the browser's native APIs to build certain UI components easily, whereas we've been using sometimes complex JS to do this for years.
 
-He showed for example:
+He shows for example:
 
 - how to build modals with [`<dialog>`](https://developer.mozilla.org/fr/docs/Web/HTML/Element/dialog) element,
 - how to easily create animated transitions with [View Transition API](https://developer.mozilla.org/en-US/docs/Web/API/View_Transitions_API) or with [`@starting-style`](https://developer.mozilla.org/en-US/docs/Web/CSS/@starting-style),
@@ -104,10 +104,11 @@ A [tweet](https://x.com/rauchg/status/807626710350839808) from [Guillermo Rauch]
 
 The talk by Sid focuses on building accessible React components, emphasizing the importance of using the correct HTML elements and [ARIA roles](https://www.w3.org/TR/wai-aria-1.2/) to enhance web accessibility.
 
-Sid highlights practical examples, such as [navigating tab lists](https://www.w3.org/WAI/ARIA/apg/patterns/tabs/) and [handling conditional checkboxes](https://www.w3.org/WAI/ARIA/apg/patterns/checkbox/), explaining how ARIA roles and properties can make web interfaces more accessible, particularly for screen reader users. 
+Sid highlights practical examples, such as [navigating tab lists](https://www.w3.org/WAI/ARIA/apg/patterns/tabs/) and [handling conditional checkboxes](https://www.w3.org/WAI/ARIA/apg/patterns/checkbox/), explaining how ARIA roles and properties can make web interfaces more accessible, particularly for screen reader users.
 
 What we will remember from this talk:
+
 - importance of using correct HTML elements and ARIA roles for accessibility.
 - implementation of ARIA roles like `tablist`, `tab`, and `aria-selected`.
 - significance of keyboard navigation and ARIA states/properties in accessibility.
-- design considerations for accessibility, including using `aria-disabled` over `disabled`.
+- design considerations for accessibility, including using `aria-disabled` over `disabled`.