part 2a

Author: pablo-maff

src/content/2/en/part2a.md

@@ -213,7 +213,7 @@ Even though the application seems to be working, there is a nasty warning in the
 
 ![unique key prop console error](../../images/2/1a.png)
 
-As the linked [React page](https://react.dev/learn/rendering-lists#keeping-list-items-in-order-with-key) in the error message suggests; the list items, i.e. the elements generated by the _map_ method, must each have a unique key value:  an attribute called <i>key</i>.
+As the linked [React page](https://react.dev/learn/rendering-lists#keeping-list-items-in-order-with-key) in the error message suggests; the list items, i.e. the elements generated by the _map_ method, must each have a unique key value: an attribute called <i>key</i>.
 
 Let's add the keys:
 
@@ -268,7 +268,6 @@ const notes = [
 
 Let's pause for a moment and examine how _map_ works.
 
-
 If the following code is added to, let's say, the end of the file:
 
 ```js
@@ -279,7 +278,6 @@ console.log(result)
 <i>[1, 2, 3]</i>  will be printed to the console.
  _map_ always creates a new array, the elements of which have been created from the elements of the original array by <i>mapping</i>: using the function given as a parameter to the _map_ method. 
 
-
 The function is
 
 ```js
@@ -539,7 +537,7 @@ const Course = ({ course }) => {
 }
 ```
 
-Quite often the root of the problem is that the props are expected to be of a different type, or called with a different name than they actually are, and destructuring fails as a result. The problem often begins to solve itself when destructuring is removed and we see what the <em>props</em> contain.
+Quite often the root of the problem is that the props are expected to be of a different type, or called with a different name than they actually have, and destructuring fails as a result. The problem often begins to solve itself when destructuring is removed and we see what the <em>props</em> contain.
 
 ```js
 const Course = (props) => { // highlight-line