Docs: remove dead links in 102

Signed-off-by: Solomon Hykes <solomon@dagger.io>

docs/learn/102-dev.md

@@ -19,11 +19,11 @@ configuration.
 
 An environment is made of 3 parts:
 
-* A *plan*, authored by the environment's *developer*, using the [Cue](https://cuelang.org) language. [Learn more about plans](FIXME)
+* A *plan*, authored by the environment's *developer*, using the [Cue](https://cuelang.org) language.
 
-* *Inputs*, supplied by the environment's *user* via the `dagger input` command, and written to a special file. Inputs may be configuration values, artifacts, or encrypted secrets. [Learn more about inputs](FIXME)
+* *Inputs*, supplied by the environment's *user* via the `dagger input` command, and written to a special file. Inputs may be configuration values, artifacts, or encrypted secrets.
 
-* *Outputs*, computed by the Dagger engine via the `dagger up` command, and recorded to a special directory. [Learn more about outputs](FIXME)
+* *Outputs*, computed by the Dagger engine via the `dagger up` command, and recorded to a special directory.
 
 We will first develop our environment's *plan*, then configure its initial inputs, then finally run it to verify that it works.
 
@@ -124,8 +124,8 @@ The first component of our plan is the source code of our React application.
 
 In Dagger terms, this component has 2 important properties:
 
-1. It is an [artifact](FIXME): something that can be represented as a directory.
-2. It is an [input](FIXME): something that is provided by the end user.
+1. It is an *artifact*: something that can be represented as a directory.
+2. It is an *input*: something that is provided by the end user.
 
 Let's write the corresponding Cue code to `multibucket-source.cue`:
 
@@ -210,7 +210,7 @@ dagger doc dagger.io/netlify
 dagger doc dagger.io/js/yarn
 ```
 
-You can also browse the [API reference](/api/FIXME) section of the documentation.
+You can also browse the [Dagger Universe](/reference/universe) reference in the documentation.
 
 ## Setup the environment