ooops

Author: honzajavorek

sources/academy/platform/scraping_with_apify_and_ai/04_docs_driven_prompting.md

@@ -1,27 +1,24 @@
 ---
-title: Tests driven prompting
+title: Docs driven prompting
 description: TBD
-slug: /scraping-with-apify-and-ai/tests-driven-prompting
+slug: /scraping-with-apify-and-ai/docs-driven-prompting
 unlisted: true
 ---
 
 <!--
-Adding fixtures, expectations. Setting up tests and teaching the agent to run tests. Dealing with corner cases by pointing the agent to the fixtures.
-
-In lesson 3, students would try to make changes via ChatGPT and see that it gets tedious, which leads to introducing an agent-based IDE to work inside the template more comfortably.
+Improving the README, e.g. input output. Pointing the agent to the README and turning the design to reality.
 -->
 
 :::note Course under construction
 This page hasn't been written yet. Come later, please!
 :::
 
-<!--
-#### Creating README.md
-Create simple README.md where we document how the scraper behaves, what it produces as an output, etc. Primer to Markdown.
-#### Dealing with price intervals
-Explain focus on product and domain knowledge. In the README explain how the scraper should handle prices like "From $1,398.00", introduce minPrice, keep prices as numbers, etc.
 
-Let the agent implement handling of variants based on the README. Run updated code, see results.
+<!--
+#### Creating tests
+Explain tests, expectations. Create test folder, drop downloaded HTML of the listing there, let the agent set up tests around it. Let the agent run tests.
+#### Scrape product variants
+Change README so that it describes how the product variants should be handled. Drop HTML of the product detail page to the tests folder. Prompt the agent to implement scraping product variants. Run the program, get results.
 
-Teaser: Imagine the target website changes something (happens often!). In such case the README won't help. Let's deal with that.
+Teaser: In the next lesson we'll learn how to deploy a similar scraper to a platform, schedule it to run regularly, automatically produce various formats, have a history of data, etc.
 -->

sources/academy/platform/scraping_with_apify_and_ai/05_tests_driven_prompting.md

@@ -1,24 +1,27 @@
 ---
-title: Docs driven prompting
+title: Tests driven prompting
 description: TBD
-slug: /scraping-with-apify-and-ai/docs-driven-prompting
+slug: /scraping-with-apify-and-ai/tests-driven-prompting
 unlisted: true
 ---
 
 <!--
-Improving the README, e.g. input output. Pointing the agent to the README and turning the design to reality.
+Adding fixtures, expectations. Setting up tests and teaching the agent to run tests. Dealing with corner cases by pointing the agent to the fixtures.
+
+In lesson 3, students would try to make changes via ChatGPT and see that it gets tedious, which leads to introducing an agent-based IDE to work inside the template more comfortably.
 -->
 
 :::note Course under construction
 This page hasn't been written yet. Come later, please!
 :::
 
-
 <!--
-#### Creating tests
-Explain tests, expectations. Create test folder, drop downloaded HTML of the listing there, let the agent set up tests around it. Let the agent run tests.
-#### Scrape product variants
-Change README so that it describes how the product variants should be handled. Drop HTML of the product detail page to the tests folder. Prompt the agent to implement scraping product variants. Run the program, get results.
+#### Creating README.md
+Create simple README.md where we document how the scraper behaves, what it produces as an output, etc. Primer to Markdown.
+#### Dealing with price intervals
+Explain focus on product and domain knowledge. In the README explain how the scraper should handle prices like "From $1,398.00", introduce minPrice, keep prices as numbers, etc.
+
+Let the agent implement handling of variants based on the README. Run updated code, see results.
 
-Teaser: In the next lesson we'll learn how to deploy a similar scraper to a platform, schedule it to run regularly, automatically produce various formats, have a history of data, etc.
+Teaser: Imagine the target website changes something (happens often!). In such case the README won't help. Let's deal with that.
 -->