Refreshed screenshots, changed name of issue_details into operations, adjusted Alt labels

Author: dfreniche

docs/30-schema-in-postgresql.mdx

@@ -2,7 +2,7 @@ import Screenshot from "@site/src/components/Screenshot";
 
 # 📘 Schema in PostgreSQL
 
-The following screenshot shows an entity-relationship diagram of the relational database we wish to migrate. This is a library management app that stores information about books, where a book can have many authors, an author can write many books, and users can borrow books and leave reviews. You can have many copies of the same book (issue_details) and those are what users borrow and return. A library user can have many addresses.
+The following screenshot shows an entity-relationship diagram of the relational database we wish to migrate. This is a library management app that stores information about books, where a book can have many authors, an author can write many books, and users can borrow books and leave reviews. You can have many copies of the same book and those are what users borrow and return. All this is registered in the `operations` collection. A library user can have many addresses.
 
 This is the sample schema we use during our [Developer Days's Intro Lab](https://mongodb-developer.github.io/intro-lab/docs/importing-data/intro).
 

docs/50-create-project/80-define-initial-schema.mdx

@@ -12,7 +12,8 @@ Select the five collections that we want as they are the main Entities in our sc
 
 - authors
 - books
-- issue_detials
+- languages
+- operations
 - reviews
 - users
 

docs/60-project-settings.mdx

@@ -7,7 +7,10 @@ import Screenshot from "@site/src/components/Screenshot";
 - Select single inherited primary key. This detects the primary key from the relational schema and sets them as the `_id` in MongoDB.
 - Optionally, toggle Suggested Mappings on and off. 
 
+
+:::info
 If we don't do this we'll have both an autogenerated `_id` field of type `ObjectId` and a `id` field copied from the relational DB.
+:::
 
 <Screenshot url="http://127.0.0.1:8278" src="img/90-image-001.png" alt="Screenshot of the connect modal" />
 

docs/80-edit-mapping-rules/10-edit-mapping-books-book-attribute.mdx

@@ -1,9 +1,9 @@
 import Screenshot from "@site/src/components/Screenshot";
 
-# 👐 Clean book attributes up  
+# 👐 Clean up book attributes  
 
 
-We want to clean up the book_attributes array in our MongoDB schema. We want an array of objects containing attributes, modelled a key value pairs. something like:
+We want to clean up the bookAttributes array in our MongoDB schema. We want an array of objects containing attributes, modelled as key value pairs. something like:
 
 ```json
 {
@@ -32,4 +32,4 @@ We want to clean up the book_attributes array in our MongoDB schema. We want an
 Here we've implemented the [Attribute Pattern](https://www.mongodb.com/developer/products/mongodb/attribute-pattern/) for MongoDB. This will allow for easy indexing, querying based on attributes and extension of attributes. 
 :::
 
-<Screenshot url="http://127.0.0.1:8278" src="img/150-image-001.png" alt="Screenshot of the connect modal" />
+<Screenshot url="http://127.0.0.1:8278" src="img/150-image-001.png" alt="Changes in the books collection" />

docs/80-edit-mapping-rules/100-edit-mapping-issue-detail-issue-detail.mdx

@@ -1,19 +1,19 @@
 import Screenshot from "@site/src/components/Screenshot";
 
-# 🦸 Remove unnecessary ids from issueDetails
+# 🦸 Remove unnecessary ids from operations
 
 :::info
 Extra activity! Do it if you have extra time or are following along at home. It won't be covered during the hands-on lab.
 :::
 
-Now we want to remove some unncessary id fields from the issueDetails collection. We have `bookId` and `userId` but we also have these values in the embedded `book` and `user` fields.
+Now we want to remove some unncessary id fields from the operations collection. We have `bookId` and `userId` but we also have these values in the embedded `book` and `user` fields.
 
-- On the MongoDB diagram view, click the `issueDetails` collection.
-- On the relational mappings list on the right, click on the edit icon of `issue_details` New Documents mapping rule.
+- On the MongoDB diagram view, click the `operations` collection.
+- On the relational mappings list on the right, click on the edit icon of `opperations` New Documents mapping rule.
 - Uncheck the `bookId` and `userId` fields, and leave all other fields checked.
 - Click `Save and close`.
 
 
 
-<Screenshot url="http://127.0.0.1:8278" src="img/190-image-001.png" alt="Screenshot of the connect modal" />
+<Screenshot url="http://127.0.0.1:8278" src="img/190-image-001.png" alt="Changes in the operations collection" />
 

docs/80-edit-mapping-rules/120-users-addresses.mdx

@@ -8,13 +8,13 @@ Extra activity! Do it if you have extra time or are following along at home. It
 
 The array that holds user addresses has a lot of unneeded data.
 
-- On the MongoDB diagram view, click on the `users` collection
-- Click on the edit edit icon of `userAddresses`
+- On the MongoDB diagram view, click on the `users` collection.
+- Click on the edit edit icon of `user_addresses` Embedded array.
 - Change the field name from `userAddresses` to `addresses`.
 - Deselect `id`, `userId` and `cityId`.
 - Click `Save and close `
 - Click on the edit edit icon of `cities`, which is an embedded document inside the array `addresses`.
-- Deselect `id`.
+- Deselect `id` and `countryId`.
 - Rename the `name` field into `cityName`.
 - In the advanced settings, check 'Merge fields into parent`.
 - Click `Save and close`.

docs/80-edit-mapping-rules/20-edit-mapping-books-book-genre.mdx

@@ -38,5 +38,5 @@ genres: [
 
 
 
-<Screenshot url="http://127.0.0.1:8278" src="img/160-image-001.png" alt="Screenshot of the connect modal" />
+<Screenshot url="http://127.0.0.1:8278" src="img/160-image-001.png" alt="Changes in the books collection" />
 

docs/80-edit-mapping-rules/30-add-mapping-books-authors.mdx

@@ -15,7 +15,7 @@ We want to modify the MongoDB schema so that each book contains an array of its
 - Click `Save and close` 
 
 
-<Screenshot url="http://127.0.0.1:8278" src="img/130-image-001.png" alt="Screenshot of the connect modal" />
+<Screenshot url="http://127.0.0.1:8278" src="img/130-image-001.png" alt="Changes in the books collection" />
 
 ## 👐 Remove unneeded bookId from author details in books collection
 
@@ -40,7 +40,7 @@ This results in our `authors` array looking like:
     ]
 ```
 
-<Screenshot url="http://127.0.0.1:8278" src="img/140-image-001.png" alt="Screenshot of the connect modal" />
+<Screenshot url="http://127.0.0.1:8278" src="img/140-image-001.png" alt="Changes in the books collection" />
 
 
 :::info

docs/80-edit-mapping-rules/50-add-mapping-books-reviews.mdx

@@ -24,5 +24,5 @@ Limitations:
 - Continuous Migration Mode will not support this transformation
 - You will not be able to enable Data Verification when you create the Migration Job.
 
-<Screenshot url="http://127.0.0.1:8278" src="img/150-image-002.png" alt="Screenshot of the connect modal" />
+<Screenshot url="http://127.0.0.1:8278" src="img/150-image-002.png" alt="Changes in the books collection" />
 

docs/80-edit-mapping-rules/60-edit-mapping-authors-alias.mdx

@@ -10,5 +10,5 @@ We want to modify the MongoDB schema so that each author's aliases are represent
 - In the mapping rule's advanced settings, Check `create array of primitive values`.
 - Click `Save and close`.
 
-<Screenshot url="http://127.0.0.1:8278" src="img/110-image-001.png" alt="Screenshot of the connect modal" />
+<Screenshot url="http://127.0.0.1:8278" src="img/110-image-001.png" alt="Changes in the authors collection" />