Fixes a couple of stale links in mojo/public/cpp/bindings/README.md

mojo/public/cpp/bindings/README.md

 # Mojo C++ Bindings API
 This document is a subset of the [Mojo documentation](/mojo).
 
 [TOC]
 
 ## Overview
 The Mojo C++ Bindings API leverages the
 [C++ System API](/mojo/public/cpp/system) to provide a more natural set of
 primitives for communicating over Mojo message pipes. Combined with generated
 code from the [Mojom IDL and bindings generator](/mojo/public/tools/bindings),
@@ skipping 990 matching lines @@
 The correct answer is, "Yes! That would be nice!" And fortunately, it can!
 
 ### Global Configuration
 
 While this feature is quite powerful, it introduces some unavoidable complexity
 into build system. This stems from the fact that type-mapping is an inherently
 viral concept: if `gfx::mojom::Rect` is mapped to `gfx::Rect` anywhere, the
 mapping needs to apply *everywhere*.
 
 For this reason we have a few global typemap configurations defined in
-[chromium_bindings_configuration.gni](https://cs.chromium.com/chromium/src/mojo/public/tools/bindings/chromium_bindings_configuration.gni)
+[chromium_bindings_configuration.gni](https://cs.chromium.org/chromium/src/mojo/public/tools/bindings/chromium_bindings_configuration.gni)
 and
-[blink_bindings_configuration.gni](https://cs.chromium.com/chromium/src/mojo/public/tools/bindings/blink_bindings_configuration.gni). These configure the two supported [variants](#Variants) of Mojom generated
+[blink_bindings_configuration.gni](https://cs.chromium.org/chromium/src/mojo/public/tools/bindings/blink_bindings_configuration.gni). These configure the two supported [variants](#Variants) of Mojom generated
 bindings in the repository. Read more on this in the sections that follow.
 
 For now, let's take a look at how to express the mapping from `gfx::mojom::Rect`
 to `gfx::Rect`.
 
 ### Defining `StructTraits`
 
 In order to teach generated bindings code how to serialize an arbitrary native
 type `T` as an arbitrary Mojom type `mojom::U`, we need to define an appropriate
 specialization of the
@@ skipping 135 matching lines @@
 `//ui/gfx/typemaps.gni` file with the following contents:
 
 ```
 typemaps = [
   "//ui/gfx/geometry/mojo/geometry.typemap",
 ]
 ```
 
 And finally we can reference this file in the global default (Chromium) bindings
 configuration by adding it to `_typemap_imports` in
-[chromium_bindings_configuration.gni](https://cs.chromium.com/chromium/src/mojo/public/tools/bindings/chromium_bindings_configuration.gni):
+[chromium_bindings_configuration.gni](https://cs.chromium.org/chromium/src/mojo/public/tools/bindings/chromium_bindings_configuration.gni):
 
 ```
 _typemap_imports = [
   ...,
   "//ui/gfx/typemaps.gni",
   ...,
 ]
 ```
 
 ### StructTraits Reference
@@ skipping 242 matching lines @@
 
 ```cpp
 inline bool IsKnownEnumValue(Department value);
 ```
 
 ### Additional Documentation
 
 [Calling Mojo From Blink](https://www.chromium.org/developers/design-documents/mojo/calling-mojo-from-blink)
 :    A brief overview of what it looks like to use Mojom C++ bindings from
      within Blink code.