Update link to "C++ Dos and Don'ts" doc
Update the link to point the one in the same folder which is often more
up-to-date, for faster navigation, and more consistent doc style.
Change-Id: I37de43adfb185e9e55a8fbf409c9ede0d1b12c21
Reviewed-on: https://chromium-review.googlesource.com/c/1407913
Reviewed-by: danakj <[email protected]>
Reviewed-by: John Abd-El-Malek <[email protected]>
Commit-Queue: Xiaohan Wang <[email protected]>
Cr-Commit-Position: refs/heads/master@{#623016}diff --git a/styleguide/c++/c++.md b/styleguide/c++/c++.md
index 892505c..74286261 100644
--- a/styleguide/c++/c++.md
+++ b/styleguide/c++/c++.md
@@ -126,9 +126,8 @@
Simple accessors should generally be the only inline functions. These should be
named `unix_hacker_style()`. Virtual functions should never be declared this way.
-For more detail, consult the [C++ Dos and
-Don'ts](https://www.chromium.org/developers/coding-style/cpp-dos-and-donts)
-section on inlining.
+For more detail, consult the [C++ Dos and Don'ts](c++-dos-and-donts.md) section
+on inlining.
## Logging
@@ -355,6 +354,5 @@
* Unit tests and performance tests should be placed in the same directory as
the functionality they're testing.
- * The [C++ do's and
- don'ts](https://sites.google.com/a/chromium.org/dev/developers/coding-style/cpp-dos-and-donts)
- page has more helpful information.
+ * The [C++ Dos and Don'ts](c++-dos-and-donts.md) page has more helpful
+ information.
