move documentation admonishment to the introduction

Author: Lokathor

book_src/introduction.md

@@ -23,6 +23,11 @@ Expected subjects include:
 * Creating ergonomic wrapper functions to make the API easily used with the rest of Rust.
 * Having those wrapper functions be fully safe (in the Rust sense) when possible, or at least making them as error-proof as we can.
 
+I will be frequently linking to the documentation pages many of the the important things we deal with.
+I expect you to *actually go to those pages* and read what they say.
+I will be covering much, but I can't cover every single detail every single time.
+You should **always** read the documentation for yourself as well as reading this tutorial.
+
 **Reminder:** The "absolutely no dependencies" thing is for demonstration purposes only.
 If you actually want to draw a triangle within a reasonable amount of development time, please do feel free to use dependencies.
-Depending on what you need to do, there's generally many good crates available.
+Depending on what you need to do, there's generally many good crates available.

book_src/opening_a_window/win32.md

@@ -8,11 +8,6 @@ There's also some C++ oriented APIs for interacting with Windows as well (called
 It's *much* easier for Rust to bind to and interact with a C oriented API than a C++ oriented API,
 so we'll start with just using Win32 to interact with Windows.
 
-**Note:** I will be linking to the MSDN pages for nearly all the important things we deal with.
-I expect you to *actually go to those pages* and read what they say.
-I will be covering much of what they deal with, but I can't cover every single detail.
-You should **always** read the documentation for yourself as well as reading this tutorial.
-
 ## Search The Web
 
 Okay, for the sake of the lesson let's pretend that *even I* don't know what to do.