Add link

docs/build/build-guide.md

@@ -35,7 +35,7 @@ development to user-facing applications:
 <!-- prettier-ignore -->
 <!-- no toc -->
 
-1. [Runtime Development - Developing parachains/blockchains](#building-parachains-tasks)
+1. [Runtime Development - Developing parachains/blockchains](#building-parachains)
 2. [Smart Contract Development - How Polkadot handles smart contracts](#developing-smart-contracts)
 3. [dApp Development - The tools available for dApp development on Polkadot](#developing-a-dapp)
 

docs/build/build-guides-coretime-start.md

@@ -18,10 +18,10 @@ Polkadot.
 
 :::
 
-## Polkadot SDK
+## Using the Polkadot SDK
 
 At first glance, the Polkadot SDK can be rather overwhelming, and in a way it is - it packs a lot of
-tech into one place. The Polkadot SDK used to be overarching **three** respositories:
+tech into one place. The Polkadot SDK used to be overarching **three** repositories:
 
 - **Polkadot** - Which for a time, included both the client implementation and runtime, until the
   runtime was moved to the Polkadot Fellows organization.
@@ -30,9 +30,19 @@ tech into one place. The Polkadot SDK used to be overarching **three** resposito
 - **Cumulus** - A set of libraries and tools which pertain specifically with connecting blockchains
   to Polkadot, known as parachains.
 
-> For an in-depth dive into the monorepo, I highly recommend you look into the
+> For an in-depth dive into the monorepo, it is highly recommended that you look into the
 > [Polkadot SDK Docs, which explains everything.](https://paritytech.github.io/polkadot-sdk/master/polkadot_sdk_docs/polkadot_sdk/index.html)
 
+:::info What is a task?
+
+You might see the term "task" referenced quite a bit, but in most cases, it refers to a process
+utilizing Polkadot's compute. This could be a parachain or any other computational process, provided
+that it adheres to the Polkadot protocol.
+
+The full definition can be found [here](../learn/learn-agile-coretime.md#task).
+
+:::
+
 ## Deploying on a Core
 
 Once you have your runtime and pallets developed, you will be able to deploy it on a
@@ -41,21 +51,17 @@ Once you have your runtime and pallets developed, you will be able to deploy it
 
 1. **Reserving** a [`ParaId`](../general/glossary.md#paraid), where you will upload your runtime and
    genesis state.
-2. **Compiling** the runtime (written in Rust) to a WebAssembly blob, thereby defining how your
-   state transitions from one state to the next. This runtime is created using the Polkadot SDK. 2a.
-   **Ensure** your chain spec is viable and ready to be deployed as a live, working parachain.
+2. **Compiling** the runtime (written in Rust) to a [WebAssembly](../learn/learn-wasm.md) blob,
+   thereby defining how your state transitions from one state to the next. This runtime is created
+   using the Polkadot SDK. 2a. **Ensure** your chain spec is viable and ready to be deployed as a
+   live, working parachain.
 3. **Generating** your genesis state and wasm.
 4. **Obtaining** a core, most likely through a
    [Coretime marketplace](../learn/learn-guides-coretime-marketplaces.md).
 5. **Assigning** that core to your[ `ParaId`](../general/glossary.md#paraid).
 6. **Ensuring** you have at least one honest, synced collator for your task
 
-:::info What is a task?
-
-You might see the term "task" referenced quite a bit, but in most cases, it refers to a process
-utilizing Polkadot's compute. This could be a parachain or any other computational process, provided
-that it adheres to the Polkadot protocol.
-
-The full definition can be found here.
+### Deploy adder collator
 
-:::
+Try out the above by deploying the
+[adder collator, a very simple "counter" parachain implementation.](../learn/learn-guides-coretime-parachains.md).