Basic layout

Author: mstephen19

content/academy/puppeteer_playwright/common_use_cases.md

@@ -0,0 +1,15 @@
+---
+title: VII - Common use cases
+description: description
+menuWeight: 7.7
+paths:
+    - puppeteer-playwright/common-use-cases
+---
+
+# [](#common-use-cases) Common use cases
+
+<!-- We'll go over login flow, pagination, etc. -->
+
+# [](#next) Next up
+
+<!-- about the next lesson -->

content/academy/puppeteer_playwright/common_use_cases/logging_into_a_website.md

@@ -0,0 +1,21 @@
+---
+title: Logging into a website
+description: description
+menuWeight: 1
+paths:
+    - puppeteer-playwright/common-use-cases/logging-into-a-website
+---
+
+# [](#logging-into-a-website) Logging into a website
+
+Whether it's auto-renewing a service, automatically sending a message on an interval, or automatically cancelling a Netflix subscription, one of the most popular things headless browsers are used for is automating things within a user's account on a certain website. Of course, automating anything on a user's account requires the automation of the login process as well. In this lesson, we'll be covering how to build a simple login flow from start to finish with Playwright or Puppeteer.
+
+> In this lesson, we'll be using [yahoo.com](https://yahoo.com) as an example. Feel free to follow along using the academy Yahoo account credentials, or even deviate from the lesson a bit and try building a login flow for a different website of your choosing!
+
+## [](#inputting-credentials) Inputting credentials
+
+<!--
+1. Login (single concurrency)
+2. After enqueue new requests
+3. Pass cookies around
+-->

content/academy/puppeteer_playwright/page/waiting.md

@@ -67,7 +67,7 @@ Though in theory this is correct, it can result in a race condition in which the
 await Promise.all([page.waitForNavigation(), page.click('.g a')]);
 ```
 
-Though the line of cod above is also valid in Playwright, it is recommended to use [`page.waitForLoadState('load')`](https://playwright.dev/docs/api/class-page#page-wait-for-load-state) instead of `page.waitForNavigation()`, as it automatically handles the issues being solved in by using `Promise.all()`.
+Though the line of code above is also valid in Playwright, it is recommended to use [`page.waitForLoadState('load')`](https://playwright.dev/docs/api/class-page#page-wait-for-load-state) instead of `page.waitForNavigation()`, as it automatically handles the issues being solved by using `Promise.all()`.
 
 ```JavaScript
 await page.click('.g a');