From 8ff1aeb96d12b2a64ec3bc2b3190ce1589a227a4 Mon Sep 17 00:00:00 2001
From: Brian Kung <2836167+briankung@users.noreply.github.com>
Date: Mon, 21 Sep 2020 08:20:00 -0500
Subject: [PATCH] Add link to custom targets (#857)

This makes it slightly easier to find out more about the JSON file that specifies custom targets.
---
 .../second-edition/posts/02-minimal-rust-kernel/index.md       | 3 ++-
 1 file changed, 2 insertions(+), 1 deletion(-)

diff --git a/blog/content/second-edition/posts/02-minimal-rust-kernel/index.md b/blog/content/second-edition/posts/02-minimal-rust-kernel/index.md
index f66aaa6c..ff6dd6f3 100644
--- a/blog/content/second-edition/posts/02-minimal-rust-kernel/index.md
+++ b/blog/content/second-edition/posts/02-minimal-rust-kernel/index.md
@@ -104,8 +104,9 @@ Cargo supports different target systems through the `--target` parameter. The ta
 [target triple]: https://clang.llvm.org/docs/CrossCompilation.html#target-triple
 [ABI]: https://stackoverflow.com/a/2456882
 [platform-support]: https://forge.rust-lang.org/release/platform-support.html
+[custom-targets]: https://doc.rust-lang.org/nightly/rustc/targets/custom.html
 
-For our target system, however, we require some special configuration parameters (e.g. no underlying OS), so none of the [existing target triples][platform-support] fits. Fortunately, Rust allows us to define our own target through a JSON file. For example, a JSON file that describes the `x86_64-unknown-linux-gnu` target looks like this:
+For our target system, however, we require some special configuration parameters (e.g. no underlying OS), so none of the [existing target triples][platform-support] fits. Fortunately, Rust allows us to define [our own target][custom-targets] through a JSON file. For example, a JSON file that describes the `x86_64-unknown-linux-gnu` target looks like this:
 
 ```json
 {