diff --git a/content/1_Intro/Modules.mdx b/content/1_Intro/Modules.mdx
index af7f0ec..a02d087 100644
--- a/content/1_Intro/Modules.mdx
+++ b/content/1_Intro/Modules.mdx
@@ -5,48 +5,50 @@ author: Nathan Wang, Benjamin Qi
description: How this guide is organized.
---
-All material in this guide will be grouped into **modules** such as the one you're reading right now.
+The material in this guide will be grouped into **modules** such as the one you're reading right now. A module will consist of several resources, practice problems, and additional content specific to the module.
-## Lesson
-
- - Goal is to introduce you to the concept.
+## Lesson
+ - The goal is to introduce you to the concept.
- Everything is meant to be completed in order.
- - Usually begins with at least one standard problem.
- - External resources (text, possibly videos) will generally be placed in tables like the one above. We'll **star** those that we expect you to read.
+ - Usually begins with at least one standard problem, marked "Intro" in the difficulty column.
+
+ - External resources will be placed in tables like the one above. We'll **star** those that we highly recommend you read.
-If we expect you to spend time thinking about a sample problem before checking the solution we'll place the solution in **spoiler blocks** like this.
+In some modules, codes or solutions will be placed in **spoiler blocks** like this. In these cases, you should think about the problem or try to implement it yourself before revealing the solution or code.
-It's okay to skip over these. Some material in these boxes might not be useful for competitive programming.
+Not all content in this guide is essential to competitive programming. Skipping over optional content is fine, but if you're interested, feel free to explore further as well.
## Implementations
-Code should compile by itself, example input / output should be provided. Macros should generally be avoided.
+All implementations should compile, have example input / output provided, and have relatively few macros. If any code does not compile or is hard to read, submit a complaint using the "Contact Us" tab.
- For Bronze, we will provide code snippets in C++, Java, and Python.
- - For Silver and Gold, we will provide code snippets in C++ and Java and (sometimes) Python.
+ - For Silver and Gold, we will provide code snippets in C++ and Java and sometimes Python.
- For Platinum, code snippets might only be provided in C++.
-Will contain common errors that you should avoid.
+A warning block like this will contain common errors that you should avoid.
-(code style guide?)
+
## Practice
-Maybe helpful bits of advice.
+Helpful bits of advice provided by the author.
+
+
@@ -54,9 +56,13 @@ Maybe helpful bits of advice.
- Problems should be sorted in order of how they are recommended be completed.
- Add comments regarding solution sketches.
- At some point we'll write full editorials for those problems which don't have them (or if existing editorials are poorly written).
- - Difficulty ranges from "Very Easy" to "Insane." Difficulty is **not** comparable across modules (even of the same division).
+ - Difficulty ranges from "Very Easy" to "Insane." Difficulty is **not** comparable across modules (even of the same division), but rather relative to the topic
- "Intro" refers to a problem that just asks you to implement a standard algorithm or data structure.
-
+ - "Easy" refers to a problem that can be solved relatively quickly be someone who is familiar with the module, while also approachable by someone who has just finished reading the starred resources.
+ - "Medium" refers to a problem which requires a bit more thinking, but can also be solved by people who have done sufficent practice of easy problems.
+ - "Hard" refers to a problem which may take a lot of time to approach. However, if someone has done a large number of "Medium" problems and has a strong understanding of a topic, could theoretically be solved during a USACO contest.
+ - "Very Hard" refers to a problem that will challenge even very strong contestants and often requires multiple levels of observations and more knowledge than provided by the module.
+ - "Insane" refers to problems that are often horribly misplaced in their division. These problems are often a bad representation of the difficulty of problems in a USACO division. However, this does not mean that these problems cannot be interesting. If you want a challenge, try them out.
\ No newline at end of file
+Old gold problems should probably be bumped up one level. -->
+
+
+
+
+
-
\ No newline at end of file
+
+