Doc: github.com/plt -> github.com/racket

pkgs/racket-doc/scribblings/guide/guide.scrbl

@@ -16,7 +16,7 @@ into details---covering much of the Racket toolbox, but leaving
 precise details to @|Racket| and other reference manuals.
 
 @margin-note{The source of this manual is available on
-@hyperlink["https://github.com/plt/racket/tree/master/pkgs/racket-doc/scribblings/guide"]{GitHub}.}
+@hyperlink["https://github.com/racket/racket/tree/master/pkgs/racket-doc/scribblings/guide"]{GitHub}.}
 
 @table-of-contents[]
 

pkgs/racket-doc/scribblings/inside/overview.scrbl

@@ -41,7 +41,7 @@ source distribution from @url{http://download.racket-lang.org};
 detailed build instructions are in the @filepath{README} file in the
 top-level @filepath{src} directory. You can also get the latest
 sources from the @tt{git} repository at
-@url{https://github.com/plt/racket}, but beware that the repository is
+@url{https://github.com/racket/racket}, but beware that the repository is
 one step away from a normal source distribution, and it provides build
 modes that are more suitable for developing Racket itself; see
 @filepath{INSTALL.txt} in the @tt{git} repository for more

pkgs/racket-doc/scribblings/reference/reference.scrbl

@@ -32,7 +32,7 @@ friendlier (though less precise and less complete) overview of the
 language.
 
 @margin-note{The source of this manual is available on
-@hyperlink["https://github.com/plt/racket/tree/master/pkgs/racket-doc/scribblings/reference"]{GitHub}.}
+@hyperlink["https://github.com/racket/racket/tree/master/pkgs/racket-doc/scribblings/reference"]{GitHub}.}
 
 @defmodulelang*[(racket/base racket)
                 ;; Use sources for overlap with `scheme' and `mzscheme':

pkgs/racket-doc/scribblings/style/testing.scrbl

@@ -16,7 +16,7 @@ Most of our collections come with test suites. These tests suites tend to
 Run the test suites before you commit. To facilitate testing, we urge you
  to add a @tt{TESTME.txt} file to your collections. Ideally, you may also
  wish to have a file in this directory that runs the basic tests.  See the
- @hyperlink["https://github.com/plt/racket/tree/master/collects/2htdp/"]{2htdp},
+ @hyperlink["https://github.com/racket/racket/tree/master/collects/2htdp/"]{2htdp},
  which is one of the collections with its own testing style.  The file should
  describe where the tests are located, how to run these tests, and what to
  look for in terms of successes and failures. These files are necessary
@@ -30,7 +30,7 @@ After you commit, watch for and read(!)
  parts: @tt{success} and @tt{failure}. The former is for tests that should
  succeed now, and the latter is for tests that are currently expected to
  fail. See the
- @hyperlink["https://github.com/plt/racket/tree/master/collects/tests/typed-scheme"]{Typed
+ @hyperlink["https://github.com/racket/racket/tree/master/collects/tests/typed-scheme"]{Typed
  Racket testing arrangement} for an example. When you create such
  @tt{failure} tests, you may wish to disable DrDr's checking like this:
 @verbatim[#:indent 2]{

racket/src/native-libs/README.txt

@@ -123,7 +123,7 @@ Build Steps (assuming no version changes)
 
    where <native-pkgs-dir> contains the package "source" directories,
    such as "draw-win32-i386". The <native-pkgs-dir> is normally a
-   checkout of "https://github.com/plt/libs.git".
+   checkout of "https://github.com/racket/libs.git".
 
 Details
 -------

racket/src/worksp/README

@@ -121,7 +121,7 @@ supply them in binary form.
 The DLLs are distributed in packages, but they are also available
 from
  
-    https://github.com/plt/libs
+    https://github.com/racket/libs
 
 and they must be installed into