Add challenge info, lib details

README.md

@@ -1,9 +1,27 @@
 # Learn Scrypto Episode 2 :microscope: A Peek Under the Hood :dna:
 
-Picking up where we left off in episode 1 let's dig a little deeper and take a look under the hood for a minute to better understand what was created for us in our generated blueprint!
+Picking up where we left off in episode 1 let's dig a little deeper and take a look under the hood for a minute to better understand what the Scrypto CLI tool created for us in our generated blueprint!
 
 We will look at how to find more of the options and capabilities that we get from the Scrypto libraries and Radix engine. Then make our way through some other example blueprints and identify reusable patterns. In the end hopefully it will feel a bit more comfortable to compose your own custom blueprints.
 
+:tada: Next Get ready for Episode 3 where we will build out a DAO boilerplate project to kickstart your entry in the Radix Scrypto DAO Challenge where you can learn and win!
+
+A total of $15 000 worth of :coin: XRD will be divided between the author of the three best submissions. Also, everyone will get a DAO edition of the Scrypto competition NFTs (delivered once Babylon is out) and random participants will receive Radix-themed t-shirts!
+
+### How to participate in the Challenge
+
+_To participate in this Scrypto competition, please do the following:_
+
+1. Register for the challenge by reading and reacting to the message in the [#scrypto-challenges channel](https://discord.com/channels/417762285172555786/1016714714471997471) on our Discord server. This will give you access to a voice channel where we will be regularly answering questions about Scrypto and the competition.
+2. Install the [Scrypto toolchain](https://docs.radixdlt.com/main/scrypto/getting-started/install-scrypto.html) and make sure you are on version 0.5.1 with “scrypto --version”.
+3. Fork the [challenges repository](https://github.com/radixdlt/scrypto-challenges).
+4. Clone the forked repository on your local environment.
+5. Start a new scrypto project with the command “scrypto new-package [name]” inside the “5-DAO” directory.
+6. Before the deadline on October 11th, 2022 at 11:45 pm UTC, commit and push your project folder and create a pull request [here](https://github.com/radixdlt/scrypto-challenges/compare).
+7. Come say “Hi!” in the #scrypto channel of our [Discord](http://discord.gg/radixdlt) server. The community will give you a warm welcome and help you with whatever question you might have.
+
+Check out all the challenge details [here :eyes:](https://www.radixdlt.com/post/scrypto-dao-challenge-is-live)
+
 ## :brain: What you will Learn
 
 1. How to find and work with built in scrypto features
@@ -12,7 +30,7 @@ We will look at how to find more of the options and capabilities that we get fro
 
 > Bonus - The process behind understanding what a piece of code is doing and how to figure it out, potentially without even knowing a particular language or library or framework or api... you see where this is leading. We are expected to know so much as developers the way to really thrive is to learn how to quickly find answers without driving yourself crazy. **Key takeaway: the process is the important part of this lesson.**
 
-### Step 1. Clone the scrypto-examples repository
+### Step 1. Project Setup & First Peek
 
 In the location of your choice run
 
@@ -33,20 +51,20 @@ Now we can install our dependencies by running `cargo build`
 
 Now we have a project we can deploy and interact with via the `resim` radix engine simulator.
 
-First up let's find out take a look at the hello world project we did in the first episode and find out what the ResourceBuilder looks like along with Bucket, Vault and some new items not seen just yet.
+First up let's find out take a look at the hello world project we did in the first episode and find out what the _ResourceBuilder_ looks like along with _Bucket_, _Vault_ and some new items not seen just yet.
 
 We can do this a couple ways:
 
 1. Using our IDE to inspect the code brought in with our cargo crates
-2. Find the package documentation - which is [here](https://radixdlt.github.io/radixdlt-scrypto/scrypto/index.html)
+2. Find the package documentation - which is [here :eyes:](https://radixdlt.github.io/radixdlt-scrypto/scrypto/index.html)
 
 To get started open up `core/hello-world/src/lib.rs` this file is our Hello blueprint!
 
-O
+Starting at the top `use scrypto::prelude::*;` is importing the scrypto library for us to use in our blueprint.
 
-Bucket and Vault will look ordinary enough if you've worked in other languages with a type system and we will look at how to see what these custom types and others that are provided in scypto give us.
+**Bucket** & **Vault** will look ordinary enough if you've worked in other languages with a type system. We can look at these custom types and others Scrypto gives us in the docs or with the rust-analyzer plugin.
 
-But what's with the :: well in rust this is a way to interact with namespaces and ResourceBuilder is a public struct we can access from the Scrypto Crate namespace. ie if you were to write it all the way out it would look like `scrypto::resource::ResourceBuilder`
+Now what's with the :: :thinking: well in Rust this is a way to interact with namespaces(like dot notation) and ResourceBuilder is a public struct we can access from the Scrypto Crate namespace. ie if you were to write it all the way out it would look like `scrypto::resource::ResourceBuilder`
 
 Notice in this line `let my_bucket: Bucket = ResourceBuilder::new_fungible()` there is a type of Bucket being infered then the :: allows us to access the ResourceBuilder struct and call the new_fungible() function.
 
@@ -58,22 +76,26 @@ Ok so let's take a stroll through the process I use to find these answers. I'll
 
 The reason I set this project up using the examples repository rather than just generating a new project with the Scrypto CLI tool is so that we can learn the first phase of utilizing new tech.
 
-:jigsaw: **Following patterns** can help you produce demonstratable results faster, build confidence and ultimately lead to the greater understanding needed to compose your own logic from scratch with a lot less headache.
+### :jigsaw: **Following patterns**
+
+Identifying patterns can help you produce demonstratable results faster, build confidence and ultimately lead to the greater understanding needed to compose your own logic from scratch with a lot less headache.
 
 Next let's open up `core/hello-nft/src/lib.rs`
 
-We can quickly see similar elements to our Hello bluprint and also check out a couple new items here.
+We can quickly see similar elements to our Hello bluprint and also check out a couple new items here. In our first example we created a simple token and give it away for free. In this example we create a set of NFT tickets and sell them for a price. This makes a nice evolution to give us some familiar patterns and introduce a few new concepts.
 
 ### Step 3. Compose Your Own Blueprints
 
 This is where coding gets really fun, once you get comfortable composing your own logic you get to be creative and launch :rocket: those amazing ideas you come up with!
 
 > ### Useful Docs Links
 >
-> scrypto crate docs -
+> Main Radix Docs Page - https://docs.radixdlt.com/main/index.html
+>
+> Scrypto crate docs -
 > https://radixdlt.github.io/radixdlt-scrypto/scrypto/index.html
 >
-> radix_engine crate docs -
+> Radix_engine crate docs -
 > https://radixdlt.github.io/radixdlt-scrypto/radix_engine/index.html
 >
 > sbor crate docs - https://radixdlt.github.io/radixdlt-scrypto/sbor/index.html