tag all docs as moved so people can find the latest correct ones

Development has moved to the "main" branch now.

BUG=chromium:1126855

Change-Id: I6a8642c17c6e0d5c54b1e39fe96d15292f985290
Reviewed-on: https://chromium-review.googlesource.com/c/chromiumos/docs/+/2653890
Reviewed-by: Trent Begin <tbegin@chromium.org>
Tested-by: Mike Frysinger <vapier@chromium.org>
diff --git a/README.md b/README.md
index 258416a..ccbdd66 100644
--- a/README.md
+++ b/README.md
@@ -1,5 +1,10 @@
 # Chromium OS docs
 
+*** note
+**Warning: This document is old & has moved.  Please update any links:**<br>
+https://chromium.googlesource.com/chromiumos/docs/
+***
+
 This directory contains public [Chromium OS] project documentation that is
 automatically [rendered by Gitiles]. The docs are written in [Gitiles-flavored
 Markdown].
diff --git a/adding_builder_variants.md b/adding_builder_variants.md
index a6e6c2c..e41ac15 100644
--- a/adding_builder_variants.md
+++ b/adding_builder_variants.md
@@ -1,5 +1,10 @@
 # Adding Builder Variants using Profiles
 
+*** note
+**Warning: This document is old & has moved.  Please update any links:**<br>
+https://chromium.googlesource.com/chromiumos/docs/+/HEAD/adding_builder_variants.md
+***
+
 ## Purpose
 
 This page documents the steps taken to add builders to the Chrome OS testing
diff --git a/archive_mirrors.md b/archive_mirrors.md
index a2c2d5d..350ecc1 100644
--- a/archive_mirrors.md
+++ b/archive_mirrors.md
@@ -1,5 +1,10 @@
 # Chromium OS Archive Mirrors
 
+*** note
+**Warning: This document is old & has moved.  Please update any links:**<br>
+https://chromium.googlesource.com/chromiumos/docs/+/HEAD/archive_mirrors.md
+***
+
 The Chromium OS project maintains a number of mirrors of archives.
 We do this to provide stability to our build system: if an upstream project
 deleted or modified a tarball on their website, we don't want that breaking
diff --git a/ca_certs.md b/ca_certs.md
index 3abd041..aa88e07 100644
--- a/ca_certs.md
+++ b/ca_certs.md
@@ -1,5 +1,10 @@
 # Root CA Certificates on Chromium OS
 
+*** note
+**Warning: This document is old & has moved.  Please update any links:**<br>
+https://chromium.googlesource.com/chromiumos/docs/+/HEAD/ca_certs.md
+***
+
 TLS clients need a set of root CA certificates to establish the chain of trust
 when connecting to a service on the Internet. On Chromium OS systems, three sets
 of certificates exist for different purposes:
diff --git a/chrome_commit_pipeline.md b/chrome_commit_pipeline.md
index 35279fe..441411c 100644
--- a/chrome_commit_pipeline.md
+++ b/chrome_commit_pipeline.md
@@ -1,5 +1,10 @@
 # Life of a Chrome commit on Chrome OS
 
+*** note
+**Warning: This document is old & has moved.  Please update any links:**<br>
+https://chromium.googlesource.com/chromiumos/docs/+/HEAD/chrome_commit_pipeline.md
+***
+
 This document provides a brief overview of how Chrome changes get committed
 and tested on Chrome OS.
 
diff --git a/chromeos_gn.md b/chromeos_gn.md
index 0bd774c..9d14b13 100644
--- a/chromeos_gn.md
+++ b/chromeos_gn.md
@@ -1,5 +1,10 @@
 # GN in Chrome OS (go/chromeos-gn)
 
+*** note
+**Warning: This document is old & has moved.  Please update any links:**<br>
+https://chromium.googlesource.com/chromiumos/docs/+/HEAD/chromeos_gn.md
+***
+
 New packages should use
 [GN](https://gn.googlesource.com/gn/+/HEAD/docs/reference.md) instead of GYP.
 
diff --git a/constants/README.md b/constants/README.md
index dbcbc8e..48cae70 100644
--- a/constants/README.md
+++ b/constants/README.md
@@ -1,5 +1,10 @@
 # Constants Lookup Tables
 
+*** note
+**Warning: This document is old & has moved.  Please update any links:**<br>
+https://chromium.googlesource.com/chromiumos/docs/+/HEAD/constants/README.md
+***
+
 When debugging code, it can often be useful to have a reference for constants
 and their symbolic names.
 There are a variety of sources available on the internet, some good, many bad.
diff --git a/constants/errnos.md b/constants/errnos.md
index f443df9..4bb468e 100644
--- a/constants/errnos.md
+++ b/constants/errnos.md
@@ -1,5 +1,10 @@
 # Linux Error Number Table (errno)
 
+*** note
+**Warning: This document is old & has moved.  Please update any links:**<br>
+https://chromium.googlesource.com/chromiumos/docs/+/HEAD/constants/errnos.md
+***
+
 These are the error numbers (errno) and their corresponding symbolic names.
 
 While some architectures/ABIs have different number<->symbol mappings, they're
diff --git a/constants/signals.md b/constants/signals.md
index cb3ccd2..1c74655 100644
--- a/constants/signals.md
+++ b/constants/signals.md
@@ -1,5 +1,10 @@
 # Linux Signal Table
 
+*** note
+**Warning: This document is old & has moved.  Please update any links:**<br>
+https://chromium.googlesource.com/chromiumos/docs/+/HEAD/constants/signals.md
+***
+
 These are the signal numbers and their corresponding symbolic names.
 
 While some architectures/ABIs have different number<->symbol mappings, they're
diff --git a/constants/syscalls.md b/constants/syscalls.md
index d4fc3c6..efcfe48 100644
--- a/constants/syscalls.md
+++ b/constants/syscalls.md
@@ -1,5 +1,10 @@
 # Linux System Call Table
 
+*** note
+**Warning: This document is old & has moved.  Please update any links:**<br>
+https://chromium.googlesource.com/chromiumos/docs/+/HEAD/constants/syscalls.md
+***
+
 These are the system call numbers (NR) and their corresponding symbolic names.
 
 These vary significantly across architectures/ABIs, both in mappings and in
diff --git a/contact.md b/contact.md
index 265da40..d86c32b 100644
--- a/contact.md
+++ b/contact.md
@@ -1,5 +1,10 @@
 # Chromium OS Contact
 
+*** note
+**Warning: This document is old & has moved.  Please update any links:**<br>
+https://chromium.googlesource.com/chromiumos/docs/+/HEAD/contact.md
+***
+
 The Chromium OS project has many communication channels.
 Finding out which one makes sense for your question/issue can be overwhelming.
 
diff --git a/containers_and_vms.md b/containers_and_vms.md
index e269251..0286397 100644
--- a/containers_and_vms.md
+++ b/containers_and_vms.md
@@ -1,5 +1,10 @@
 # Running Custom Containers Under Chrome OS
 
+*** note
+**Warning: This document is old & has moved.  Please update any links:**<br>
+https://chromium.googlesource.com/chromiumos/docs/+/HEAD/containers_and_vms.md
+***
+
 Welcome to the containers project where we support running arbitrary code inside
 of [VM]s in Chrome OS.
 This is a heavily-technical document; for user-friendly information, see
diff --git a/contributing.md b/contributing.md
index 5b8c61c..e69422e 100644
--- a/contributing.md
+++ b/contributing.md
@@ -1,5 +1,10 @@
 # Chromium OS Contributing Guide
 
+*** note
+**Warning: This document is old & has moved.  Please update any links:**<br>
+https://chromium.googlesource.com/chromiumos/docs/+/HEAD/contributing.md
+***
+
 For new developers & contributors, the [Gerrit] system might be unfamiliar.
 Even if you're already familiar with [Gerrit], how the Chromium project uses it
 might be different due to the [CQ]/trybot integration and different labels.
diff --git a/cros_commit_pipeline.md b/cros_commit_pipeline.md
index 54361dd..00a323d 100644
--- a/cros_commit_pipeline.md
+++ b/cros_commit_pipeline.md
@@ -1,5 +1,10 @@
 # Life of a Chrome OS commit
 
+*** note
+**Warning: This document is old & has moved.  Please update any links:**<br>
+https://chromium.googlesource.com/chromiumos/docs/+/HEAD/cros_commit_pipeline.md
+***
+
 [TOC]
 
 This document provides a brief overview of how Chrome OS changes get committed
diff --git a/cros_deploy.md b/cros_deploy.md
index 7c491f2..be35269 100644
--- a/cros_deploy.md
+++ b/cros_deploy.md
@@ -1,5 +1,10 @@
 # Cros Deploy
 
+*** note
+**Warning: This document is old & has moved.  Please update any links:**<br>
+https://chromium.googlesource.com/chromiumos/docs/+/HEAD/cros_deploy.md
+***
+
 ## Overview
 
 [`cros deploy`][script] is a script to deploy (install) a package to your
diff --git a/cros_flash.md b/cros_flash.md
index 2e90f46..23eeaa1 100644
--- a/cros_flash.md
+++ b/cros_flash.md
@@ -1,5 +1,10 @@
 # Cros Flash
 
+*** note
+**Warning: This document is old & has moved.  Please update any links:**<br>
+https://chromium.googlesource.com/chromiumos/docs/+/HEAD/cros_flash.md
+***
+
 ## Overview
 
 `cros flash` is a script to update a Chromium OS device with an image, or to
diff --git a/cros_tools.md b/cros_tools.md
index b01b8ad..90da00a 100644
--- a/cros_tools.md
+++ b/cros_tools.md
@@ -1,5 +1,10 @@
 # CrOS Tools
 
+*** note
+**Warning: This document is old & has moved.  Please update any links:**<br>
+https://chromium.googlesource.com/chromiumos/docs/+/HEAD/cros_tools.md
+***
+
 This aims to be an reference page to help find CrOS tools and their documentation.
 
 ## Tools
diff --git a/cros_vm.md b/cros_vm.md
index 1af72f4..aa73743 100644
--- a/cros_vm.md
+++ b/cros_vm.md
@@ -1,5 +1,10 @@
 # Chrome OS VM for Chromium developers
 
+*** note
+**Warning: This document is old & has moved.  Please update any links:**<br>
+https://chromium.googlesource.com/chromiumos/docs/+/HEAD/cros_vm.md
+***
+
 This workflow allows developers with a Chromium checkout using [Simple Chrome]
 to download and launch a Chrome OS VM on their workstations, update the VM with
 locally built Chrome, and run various tests.
diff --git a/crostini_developer_guide.md b/crostini_developer_guide.md
index 483df70..9ce6088 100644
--- a/crostini_developer_guide.md
+++ b/crostini_developer_guide.md
@@ -1,5 +1,10 @@
 # Crostini developer guide
 
+*** note
+**Warning: This document is old & has moved.  Please update any links:**<br>
+https://chromium.googlesource.com/chromiumos/docs/+/HEAD/crostini_developer_guide.md
+***
+
 If you just want to use Linux (Beta), you should read the [Running Custom
 Containers Under Chrome OS](containers_and_vms.md) doc. This doc is all about
 how the crostini is made, not how to use it. :)
diff --git a/dbus_best_practices.md b/dbus_best_practices.md
index f21bbdf..9f8b362 100644
--- a/dbus_best_practices.md
+++ b/dbus_best_practices.md
@@ -1,5 +1,10 @@
 # Chrome OS D-Bus Best Practices
 
+*** note
+**Warning: This document is old & has moved.  Please update any links:**<br>
+https://chromium.googlesource.com/chromiumos/docs/+/HEAD/dbus_best_practices.md
+***
+
 Chrome OS uses [D-Bus] for inter-process communication. At a high level, D-Bus
 consists of a **system bus** that is managed by a `dbus-daemon` process.
 **Clients** (typically either system daemons or Chrome) connect to the system
diff --git a/dbus_in_chrome.md b/dbus_in_chrome.md
index b74cec3..30825bb 100644
--- a/dbus_in_chrome.md
+++ b/dbus_in_chrome.md
@@ -1,5 +1,10 @@
 # Chrome OS D-Bus Usage in Chrome
 
+*** note
+**Warning: This document is old & has moved.  Please update any links:**<br>
+https://chromium.googlesource.com/chromiumos/docs/+/HEAD/dbus_in_chrome.md
+***
+
 [D-Bus] is used to perform interprocess communication on Chrome OS. This
 document describes how to use D-Bus for communication between Chrome and system
 daemons.
diff --git a/debug_buttons.md b/debug_buttons.md
index b4926f0..226a3b1 100644
--- a/debug_buttons.md
+++ b/debug_buttons.md
@@ -1,5 +1,10 @@
 # Debug Button Shortcuts
 
+*** note
+**Warning: This document is old & has moved.  Please update any links:**<br>
+https://chromium.googlesource.com/chromiumos/docs/+/HEAD/debug_buttons.md
+***
+
 Chrome OS devices provide a variety of advanced keyboard and button shortcuts
 that are useful for debugging. We document those here, as well as highlight
 some differences between devices with and without keyboards.
diff --git a/design_docs/cros_board_info.md b/design_docs/cros_board_info.md
index f59e714..34574b4 100644
--- a/design_docs/cros_board_info.md
+++ b/design_docs/cros_board_info.md
@@ -1,5 +1,10 @@
 # CBI: CrOS Board Info
 
+*** note
+**Warning: This document is old & has moved.  Please update any links:**<br>
+https://chromium.googlesource.com/chromiumos/docs/+/HEAD/design_docs/cros_board_info.md
+***
+
 [TOC]
 
 ## Terms
diff --git a/design_docs/firmware_config.md b/design_docs/firmware_config.md
index 5ebefba..74383d8 100644
--- a/design_docs/firmware_config.md
+++ b/design_docs/firmware_config.md
@@ -1,5 +1,10 @@
 # SKU and FW Configuration Fields
 
+*** note
+**Warning: This document is old & has moved.  Please update any links:**<br>
+https://chromium.googlesource.com/chromiumos/docs/+/HEAD/design_docs/firmware_config.md
+***
+
 [TOC]
 
 ## Background
diff --git a/developer_guide.md b/developer_guide.md
index 287b649..6dba2e6 100644
--- a/developer_guide.md
+++ b/developer_guide.md
@@ -1,5 +1,10 @@
 # Chromium OS Developer Guide
 
+*** note
+**Warning: This document is old & has moved.  Please update any links:**<br>
+https://chromium.googlesource.com/chromiumos/docs/+/HEAD/developer_guide.md
+***
+
 ## Introduction
 
 This guide describes how to work on Chromium OS. If you want to help develop
diff --git a/developer_mode.md b/developer_mode.md
index 9c3a823..1b2e049 100644
--- a/developer_mode.md
+++ b/developer_mode.md
@@ -1,5 +1,10 @@
 # Developer Mode
 
+*** note
+**Warning: This document is old & has moved.  Please update any links:**<br>
+https://chromium.googlesource.com/chromiumos/docs/+/HEAD/developer_mode.md
+***
+
 Production Chrome OS devices that are shipped from the factory are locked down
 and will not let you make changes to the software. This page describes how to
 enable developer mode and get root access to your system.
diff --git a/development_basics.md b/development_basics.md
index 800e0ba..9eb5016 100644
--- a/development_basics.md
+++ b/development_basics.md
@@ -1,5 +1,10 @@
 # Chromium OS Development Basics
 
+*** note
+**Warning: This document is old & has moved.  Please update any links:**<br>
+https://chromium.googlesource.com/chromiumos/docs/+/HEAD/development_basics.md
+***
+
 This document covers guidelines to keep in mind when working on the Chromium OS
 project.
 
diff --git a/eol_aue_process.md b/eol_aue_process.md
index 4fc932e..d0a8f11 100644
--- a/eol_aue_process.md
+++ b/eol_aue_process.md
@@ -1,6 +1,11 @@
 # End of Life (EOL) / Auto Update Expiration (AUE) Process
 
 *** note
+**Warning: This document is old & has moved.  Please update any links:**<br>
+https://chromium.googlesource.com/chromiumos/docs/+/HEAD/eol_aue_process.md
+***
+
+*** note
 The official Google policy can be found at
 https://support.google.com/chrome/a/answer/6220366.
 This document is purely for developers making code changes to the project.
diff --git a/firmware/coreboot_upstream.md b/firmware/coreboot_upstream.md
index b49e1ee..facfa77 100644
--- a/firmware/coreboot_upstream.md
+++ b/firmware/coreboot_upstream.md
@@ -1,5 +1,10 @@
 # Working with Coreboot upstream and Chromium
 
+*** note
+**Warning: This document is old & has moved.  Please update any links:**<br>
+https://chromium.googlesource.com/chromiumos/docs/+/HEAD/firmware/coreboot_upstream.md
+***
+
 [TOC]
 
 ## Introduction
diff --git a/firmware_code_reviews.md b/firmware_code_reviews.md
index 648fdba..1e12319 100644
--- a/firmware_code_reviews.md
+++ b/firmware_code_reviews.md
@@ -1,4 +1,10 @@
 # Firmware code review guidelines
+
+*** note
+**Warning: This document is old & has moved.  Please update any links:**<br>
+https://chromium.googlesource.com/chromiumos/docs/+/HEAD/firmware_code_reviews.md
+***
+
 ## Goals for guidelines
 
 * Minimize review latency.
diff --git a/firmware_test_manual.md b/firmware_test_manual.md
index ff8828b..1b740bd 100644
--- a/firmware_test_manual.md
+++ b/firmware_test_manual.md
@@ -1,5 +1,10 @@
 # Firmware Test Manual
 
+*** note
+**Warning: This document is old & has moved.  Please update any links:**<br>
+https://chromium.googlesource.com/chromiumos/docs/+/HEAD/firmware_test_manual.md
+***
+
 This is a Firmware test manual targeted for any tester needing to work with AP,
 EC, or GSC firmware.
 
diff --git a/git_and_gerrit_intro.md b/git_and_gerrit_intro.md
index ca8602a..1e3071c 100644
--- a/git_and_gerrit_intro.md
+++ b/git_and_gerrit_intro.md
@@ -1,5 +1,10 @@
 # Introduction to Git & Gerrit for CrOS contributors
 
+*** note
+**Warning: This document is old & has moved.  Please update any links:**<br>
+https://chromium.googlesource.com/chromiumos/docs/+/HEAD/git_and_gerrit_intro.md
+***
+
 This guide provides a brief guide to creating Git commits and getting them
 reviewed on Gerrit, for those who have not used either system before. It assumes
 that you’ve already got a local copy of the repository you want to modify, and
diff --git a/glossary.md b/glossary.md
index c93e3a8..3217899 100644
--- a/glossary.md
+++ b/glossary.md
@@ -1,5 +1,10 @@
 ## Acronyms
 
+*** note
+**Warning: This document is old & has moved.  Please update any links:**<br>
+https://chromium.googlesource.com/chromiumos/docs/+/HEAD/glossary.md
+***
+
 *   __3PL__: Third Party Labs.
 *   __ACLs__: Access Control Lists.
 *   __AFE__: Auto Test Front End.
diff --git a/gsutil.md b/gsutil.md
index 187ab99..45700ff 100644
--- a/gsutil.md
+++ b/gsutil.md
@@ -1,5 +1,10 @@
 # gsutil FAQ
 
+*** note
+**Warning: This document is old & has moved.  Please update any links:**<br>
+https://chromium.googlesource.com/chromiumos/docs/+/HEAD/gsutil.md
+***
+
 `gsutil` is a command line tool for working with Google Storage (GS) buckets.
 We use it heavily in Chromium OS to mirror our files around the world.
 
diff --git a/input_stack.md b/input_stack.md
index 1bf419f..0a9a185 100644
--- a/input_stack.md
+++ b/input_stack.md
@@ -1,5 +1,10 @@
 # Chromium OS Input Stack
 
+*** note
+**Warning: This document is old & has moved.  Please update any links:**<br>
+https://chromium.googlesource.com/chromiumos/docs/+/HEAD/input_stack.md
+***
+
 This document summarises the Chromium OS input stack, from when events leave the
 input device until the point where they enter Chromium's cross-platform code.
 Each stage includes links to debugging tools, if available.
diff --git a/kernel_development.md b/kernel_development.md
index 1b1c5e5..045f347 100644
--- a/kernel_development.md
+++ b/kernel_development.md
@@ -1,5 +1,10 @@
 # Kernel Development
 
+*** note
+**Warning: This document is old & has moved.  Please update any links:**<br>
+https://chromium.googlesource.com/chromiumos/docs/+/HEAD/kernel_development.md
+***
+
 This document covers best practices for kernel development in Chromium
 OS, including debugging tips, platform bringup info, committing
 changes, sending code upstream, and using upstream repos for testing &
diff --git a/life_of_a_bug.md b/life_of_a_bug.md
index 8aa4342..582775e 100644
--- a/life_of_a_bug.md
+++ b/life_of_a_bug.md
@@ -1,5 +1,10 @@
 # Life of a Chrome OS Bug
 
+*** note
+**Warning: This document is old & has moved.  Please update any links:**<br>
+https://chromium.googlesource.com/chromiumos/docs/+/HEAD/life_of_a_bug.md
+***
+
 [TOC]
 
 Chrome OS maintains two public issue trackers where you can report bugs and
diff --git a/logging.md b/logging.md
index 3890c39..301e006 100644
--- a/logging.md
+++ b/logging.md
@@ -1,5 +1,10 @@
 # Logging on Chrome OS
 
+*** note
+**Warning: This document is old & has moved.  Please update any links:**<br>
+https://chromium.googlesource.com/chromiumos/docs/+/HEAD/logging.md
+***
+
 ## Syslog Logs (managed by rsyslog)
 
 Services write the logs into files using syslog like a Linux. Application can call the syslog APIs, the API writes the messages into the syslog socket (/dev/log), the syslog daemon (rsyslogd) receives the message and the daemon writes it to the file.
diff --git a/lsb-release.md b/lsb-release.md
index 9220028..f3e98bd 100644
--- a/lsb-release.md
+++ b/lsb-release.md
@@ -1,5 +1,10 @@
 # /etc/lsb-release File Format
 
+*** note
+**Warning: This document is old & has moved.  Please update any links:**<br>
+https://chromium.googlesource.com/chromiumos/docs/+/HEAD/lsb-release.md
+***
+
 The `/etc/lsb-release` file is used in CrOS to hold some system settings.
 Unfortunately, nowhere is the format of this file actually documented.
 [LSB] itself only documents the `lsb_release` program.
diff --git a/os_config.md b/os_config.md
index 9f646ee..e787cc5 100644
--- a/os_config.md
+++ b/os_config.md
@@ -1,5 +1,10 @@
 # Chromium OS Configuration
 
+*** note
+**Warning: This document is old & has moved.  Please update any links:**<br>
+https://chromium.googlesource.com/chromiumos/docs/+/HEAD/os_config.md
+***
+
 Often times browser and OS programs need to change their behavior at runtime
 based on how the OS has been configured.
 Further, many of pieces of code often ask the same question (e.g. "Is dev mode
diff --git a/packages/libchrome.md b/packages/libchrome.md
index 74c92cd..03819dc 100644
--- a/packages/libchrome.md
+++ b/packages/libchrome.md
@@ -1,5 +1,10 @@
 # libchrome
 
+*** note
+**Warning: This document is old & has moved.  Please update any links:**<br>
+https://chromium.googlesource.com/chromiumos/docs/+/HEAD/packages/libchrome.md
+***
+
 [TOC]
 
 ## Background
diff --git a/pd_firmware_update.md b/pd_firmware_update.md
index 00e6ba1..0fbe9f8 100644
--- a/pd_firmware_update.md
+++ b/pd_firmware_update.md
@@ -1,5 +1,10 @@
 # USB Type-C Power Delivery (PD) Firmware
 
+*** note
+**Warning: This document is old & has moved.  Please update any links:**<br>
+https://chromium.googlesource.com/chromiumos/docs/+/HEAD/pd_firmware_update.md
+***
+
 Some Type-C Port Controller (TCPC) chips in ChromeOS Devices are programmed
 with a firmware component when shipped out of the factory. This firmware
 (sometimes called PD firmware) may be updateable in the field. The firmware
diff --git a/platform2_primer.md b/platform2_primer.md
index 7516b9c..fdea6f2 100644
--- a/platform2_primer.md
+++ b/platform2_primer.md
@@ -1,5 +1,10 @@
 # Getting started with platform2
 
+*** note
+**Warning: This document is old & has moved.  Please update any links:**<br>
+https://chromium.googlesource.com/chromiumos/docs/+/HEAD/platform2_primer.md
+***
+
 [TOC]
 
 ## What is platform2?
diff --git a/platform_public_tracker.md b/platform_public_tracker.md
index 11e5412..a3e10f3 100644
--- a/platform_public_tracker.md
+++ b/platform_public_tracker.md
@@ -1,5 +1,10 @@
 # Reporting Chrome OS bugs in the buganizer public tracker
 
+*** note
+**Warning: This document is old & has moved.  Please update any links:**<br>
+https://chromium.googlesource.com/chromiumos/docs/+/HEAD/platform_public_tracker.md
+***
+
 [TOC]
 
 Thank you for your interest in **Chrome OS!**
diff --git a/portage/ebuild_faq.md b/portage/ebuild_faq.md
index fbf43e1..e09b6ef 100644
--- a/portage/ebuild_faq.md
+++ b/portage/ebuild_faq.md
@@ -1,5 +1,10 @@
 # Ebuild FAQ
 
+*** note
+**Warning: This document is old & has moved.  Please update any links:**<br>
+https://chromium.googlesource.com/chromiumos/docs/+/HEAD/portage/ebuild_faq.md
+***
+
 
 This document aims to answer common questions about building packages used in
 developing Chromium OS.
diff --git a/portage/how_to_patch_an_ebuild.md b/portage/how_to_patch_an_ebuild.md
index 0844261..85904ac 100644
--- a/portage/how_to_patch_an_ebuild.md
+++ b/portage/how_to_patch_an_ebuild.md
@@ -1,5 +1,10 @@
 # How to Patch an Ebuild
 
+*** note
+**Warning: This document is old & has moved.  Please update any links:**<br>
+https://chromium.googlesource.com/chromiumos/docs/+/HEAD/portage/how_to_patch_an_ebuild.md
+***
+
 ## Background
 
 ChromeOS uses a package management system from Gentoo Linux called [Portage](https://wiki.gentoo.org/wiki/Portage).
diff --git a/portage/package_upgrade_process.md b/portage/package_upgrade_process.md
index 447fea3..c465fda 100644
--- a/portage/package_upgrade_process.md
+++ b/portage/package_upgrade_process.md
@@ -1,5 +1,10 @@
 # New & Upgrade Package Process
 
+*** note
+**Warning: This document is old & has moved.  Please update any links:**<br>
+https://chromium.googlesource.com/chromiumos/docs/+/HEAD/portage/package_upgrade_process.md
+***
+
 ## Purpose
 
 This page documents the process of upgrading a package in our source
diff --git a/programming_languages.md b/programming_languages.md
index 2ddb4fd..76e7675 100644
--- a/programming_languages.md
+++ b/programming_languages.md
@@ -1,5 +1,10 @@
 # Programming languages for Chrome OS
 
+*** note
+**Warning: This document is old & has moved.  Please update any links:**<br>
+https://chromium.googlesource.com/chromiumos/docs/+/HEAD/programming_languages.md
+***
+
 ## Userspace
 
 Chrome OS's userspace is predominantly written in C++, with some third-party
diff --git a/remote_trybots.md b/remote_trybots.md
index 9f09861..ea6f62c 100644
--- a/remote_trybots.md
+++ b/remote_trybots.md
@@ -1,6 +1,11 @@
 # Remote Trybots
 
 *** note
+**Warning: This document is old & has moved.  Please update any links:**<br>
+https://chromium.googlesource.com/chromiumos/docs/+/HEAD/remote_trybots.md
+***
+
+*** note
 **NOTE**: **Sorry, but this tool is only available to Google employees.**
 ***
 
diff --git a/repo-tool.md b/repo-tool.md
index 30ba86b..3648203 100644
--- a/repo-tool.md
+++ b/repo-tool.md
@@ -1,5 +1,10 @@
 # Repo tool
 
+*** note
+**Warning: This document is old & has moved.  Please update any links:**<br>
+https://chromium.googlesource.com/chromiumos/docs/+/HEAD/repo-tool.md
+***
+
 Chromium OS uses the [repo tool] to manage its [source checkout].
 
 [TOC]
diff --git a/reporting_bugs.md b/reporting_bugs.md
index 86d67e4..e37da79 100644
--- a/reporting_bugs.md
+++ b/reporting_bugs.md
@@ -1,5 +1,10 @@
 # Reporting Chrome OS bugs
 
+*** note
+**Warning: This document is old & has moved.  Please update any links:**<br>
+https://chromium.googlesource.com/chromiumos/docs/+/HEAD/reporting_bugs.md
+***
+
 [TOC]
 
 ## Chromebook Central Help Forum
diff --git a/rust_on_cros.md b/rust_on_cros.md
index f758538..963d563 100644
--- a/rust_on_cros.md
+++ b/rust_on_cros.md
@@ -1,5 +1,10 @@
 # Rust on Chrome OS
 
+*** note
+**Warning: This document is old & has moved.  Please update any links:**<br>
+https://chromium.googlesource.com/chromiumos/docs/+/HEAD/rust_on_cros.md
+***
+
 This provides information on creating [Rust] projects for installation within
 Chrome OS and Chrome OS SDK. All commands and paths given are from within the
 SDK's chroot.
diff --git a/sandboxing.md b/sandboxing.md
index 30fd6d2..04a769e 100644
--- a/sandboxing.md
+++ b/sandboxing.md
@@ -1,5 +1,10 @@
 # Sandboxing Chrome OS system services
 
+*** note
+**Warning: This document is old & has moved.  Please update any links:**<br>
+https://chromium.googlesource.com/chromiumos/docs/+/HEAD/sandboxing.md
+***
+
 [TOC]
 
 In Chrome OS, OS-level functionality (such as configuring network interfaces)
diff --git a/security/chromeos_security_whitepaper.md b/security/chromeos_security_whitepaper.md
index 3785b55..3f8b94b 100644
--- a/security/chromeos_security_whitepaper.md
+++ b/security/chromeos_security_whitepaper.md
@@ -1,5 +1,10 @@
 # Security in Chrome OS
 
+*** note
+**Warning: This document is old & has moved.  Please update any links:**<br>
+https://chromium.googlesource.com/chromiumos/docs/+/HEAD/security/chromeos_security_whitepaper.md
+***
+
 [TOC]
 
 ## Introduction
diff --git a/security/firmware_updating.md b/security/firmware_updating.md
index bcbec2e..5db93f0 100644
--- a/security/firmware_updating.md
+++ b/security/firmware_updating.md
@@ -1,5 +1,10 @@
 # Peripheral Firmware Security
 
+*** note
+**Warning: This document is old & has moved.  Please update any links:**<br>
+https://chromium.googlesource.com/chromiumos/docs/+/HEAD/security/firmware_updating.md
+***
+
 This document discusses security risks with peripheral firmware and defines
 Chrome OS' approach and requirements to address that risk.
 
diff --git a/security/handling_fuzzer_bugs.md b/security/handling_fuzzer_bugs.md
index 060ee6b..c7b33b2 100644
--- a/security/handling_fuzzer_bugs.md
+++ b/security/handling_fuzzer_bugs.md
@@ -1,5 +1,10 @@
 # Handling bugs found by fuzzers
 
+*** note
+**Warning: This document is old & has moved.  Please update any links:**<br>
+https://chromium.googlesource.com/chromiumos/docs/+/HEAD/security/handling_fuzzer_bugs.md
+***
+
 Thanks to the work of the Chrome Security Bugs-- team, the Chrome OS Toolchain
 team, and the Chrome OS security team, there is an increasing number of fuzzers
 written for Chrome OS targets. This document describes the expectations for
diff --git a/security/jit.md b/security/jit.md
index 15fe361..03af361 100644
--- a/security/jit.md
+++ b/security/jit.md
@@ -1,5 +1,10 @@
 # Just-in-time compilation in Chrome OS
 
+*** note
+**Warning: This document is old & has moved.  Please update any links:**<br>
+https://chromium.googlesource.com/chromiumos/docs/+/HEAD/security/jit.md
+***
+
 This document covers the requirements for Just-in-time (JIT) compilation on
 Chrome OS. These requirements ensure that JIT engines don't undermine the
 security guarantees of Chrome OS.
diff --git a/security/noexec_shell_scripts.md b/security/noexec_shell_scripts.md
index 4c49d0c..c00dc7b 100644
--- a/security/noexec_shell_scripts.md
+++ b/security/noexec_shell_scripts.md
@@ -1,5 +1,10 @@
 # Shell scripts & noexec mounts
 
+*** note
+**Warning: This document is old & has moved.  Please update any links:**<br>
+https://chromium.googlesource.com/chromiumos/docs/+/HEAD/security/noexec_shell_scripts.md
+***
+
 Chrome OS has added logic to the shells we ship (e.g. [dash] & [bash]) to detect
 when code is being run from `noexec` partitions.
 This can cause trouble for code that previously worked, or continues to work on
diff --git a/security/port_forwarding.md b/security/port_forwarding.md
index 0a8ea31..870d733 100644
--- a/security/port_forwarding.md
+++ b/security/port_forwarding.md
@@ -1,5 +1,10 @@
 # Port forwarding and tunneling in Chrome OS
 
+*** note
+**Warning: This document is old & has moved.  Please update any links:**<br>
+https://chromium.googlesource.com/chromiumos/docs/+/HEAD/security/port_forwarding.md
+***
+
 ## localhost to Crostini
 
 Chrome OS will forward ports from `localhost` into [Crostini]. This allows
diff --git a/security/review_process.md b/security/review_process.md
index 53f4cf3..0ec03bc 100644
--- a/security/review_process.md
+++ b/security/review_process.md
@@ -1,5 +1,10 @@
 # The Chrome OS security review process
 
+*** note
+**Warning: This document is old & has moved.  Please update any links:**<br>
+https://chromium.googlesource.com/chromiumos/docs/+/HEAD/security/review_process.md
+***
+
 This document describes the Chrome OS security review process from the security
 team's perspective. It focuses on the process itself, and how to ensure that all
 features are properly reviewed before they launch.
diff --git a/security/selinux.md b/security/selinux.md
index 37015b7..50ff029 100644
--- a/security/selinux.md
+++ b/security/selinux.md
@@ -1,5 +1,10 @@
 # SELinux in Chrome OS
 
+*** note
+**Warning: This document is old & has moved.  Please update any links:**<br>
+https://chromium.googlesource.com/chromiumos/docs/+/HEAD/security/selinux.md
+***
+
 SELinux is a kernel security module that provides ability to write accessing
 policies to archive mandatory access control.
 
diff --git a/security/sensitive_chromeos_packages.md b/security/sensitive_chromeos_packages.md
index 36518e4..072c521 100644
--- a/security/sensitive_chromeos_packages.md
+++ b/security/sensitive_chromeos_packages.md
@@ -1,5 +1,10 @@
 # Security-sensitive Chrome OS packages
 
+*** note
+**Warning: This document is old & has moved.  Please update any links:**<br>
+https://chromium.googlesource.com/chromiumos/docs/+/HEAD/security/sensitive_chromeos_packages.md
+***
+
 ## Objective
 
 This is a list of security-sensitive Portage packages that the Chrome OS team
diff --git a/security/sheriffing.md b/security/sheriffing.md
index 4a0aefb..2ee3c70 100644
--- a/security/sheriffing.md
+++ b/security/sheriffing.md
@@ -1,5 +1,10 @@
 # Chrome OS security sheriffing
 
+*** note
+**Warning: This document is old & has moved.  Please update any links:**<br>
+https://chromium.googlesource.com/chromiumos/docs/+/HEAD/security/sheriffing.md
+***
+
 ## What is sheriffing?
 
 The Chrome OS security team maintains a [security sheriff rotation] to ensure
diff --git a/security_review_howto.md b/security_review_howto.md
index 57adcb7..8e4a1ea 100644
--- a/security_review_howto.md
+++ b/security_review_howto.md
@@ -1,5 +1,10 @@
 # Chrome OS security review HOWTO
 
+*** note
+**Warning: This document is old & has moved.  Please update any links:**<br>
+https://chromium.googlesource.com/chromiumos/docs/+/HEAD/security_review_howto.md
+***
+
 This document describes the Chrome OS security review process. It's aimed at
 feature owners, tech leads, and product managers.
 
diff --git a/security_severity_guidelines.md b/security_severity_guidelines.md
index 695cff8..9866ed8 100644
--- a/security_severity_guidelines.md
+++ b/security_severity_guidelines.md
@@ -1,5 +1,10 @@
 # Chrome OS Security Severity Guidelines
 
+*** note
+**Warning: This document is old & has moved.  Please update any links:**<br>
+https://chromium.googlesource.com/chromiumos/docs/+/HEAD/security_severity_guidelines.md
+***
+
 These are the severity guidelines for Chrome OS Security Issues.
 They are related to the [Severity Guidelines for Chrome Security Issues].
 One key difference between the Chrome and Chrome OS security models is that
diff --git a/sheriff_faq.md b/sheriff_faq.md
index f4ef44e..87ba460 100644
--- a/sheriff_faq.md
+++ b/sheriff_faq.md
@@ -1,5 +1,10 @@
 # Sheriff FAQ: Chromium OS
 
+*** note
+**Warning: This document is old & has moved.  Please update any links:**<br>
+https://chromium.googlesource.com/chromiumos/docs/+/HEAD/sheriff_faq.md
+***
+
 The [thesis on Sheriffing].
 
 [TOC]
diff --git a/simple_chrome_workflow.md b/simple_chrome_workflow.md
index 52ac003..bbf2678 100644
--- a/simple_chrome_workflow.md
+++ b/simple_chrome_workflow.md
@@ -1,5 +1,10 @@
 # Building Chrome for Chrome OS (Simple Chrome)
 
+*** note
+**Warning: This document is old & has moved.  Please update any links:**<br>
+https://chromium.googlesource.com/chromiumos/docs/+/HEAD/simple_chrome_workflow.md
+***
+
 This workflow allows you to quickly build/deploy Chrome to a Chrome OS
 [VM] or device without needing a Chrome OS source checkout or chroot. It's useful
 for trying out your changes on Chrome OS while you're doing Chrome
diff --git a/source_layout.md b/source_layout.md
index ef52038..e1bcc5b 100644
--- a/source_layout.md
+++ b/source_layout.md
@@ -1,5 +1,10 @@
 # Local & Remote Source Tree Layouts
 
+*** note
+**Warning: This document is old & has moved.  Please update any links:**<br>
+https://chromium.googlesource.com/chromiumos/docs/+/HEAD/source_layout.md
+***
+
 Here we discuss the layout of files in the local source checkout as well as the
 remote Git server.
 The goal is both to document the current state of things and to provide guidance
diff --git a/stack_traces.md b/stack_traces.md
index 2a2d688..be4eae3 100644
--- a/stack_traces.md
+++ b/stack_traces.md
@@ -1,5 +1,10 @@
 # How to get a stack trace at runtime for debugging purposes
 
+*** note
+**Warning: This document is old & has moved.  Please update any links:**<br>
+https://chromium.googlesource.com/chromiumos/docs/+/HEAD/stack_traces.md
+***
+
 While debugging it's often useful to print stack traces at runtime. This
 document describes how to do so.
 
diff --git a/styleguide/README.md b/styleguide/README.md
index 24b2972..e01633e 100644
--- a/styleguide/README.md
+++ b/styleguide/README.md
@@ -1,5 +1,10 @@
 # Chromium OS Style Guide [go/cros-style]
 
+*** note
+**Warning: This document is old & has moved.  Please update any links:**<br>
+https://chromium.googlesource.com/chromiumos/docs/+/HEAD/styleguide/README.md
+***
+
 As a general rule, we try to follow existing style guides of parent projects
 when they have one.
 
diff --git a/styleguide/python.md b/styleguide/python.md
index d56b995..18441db 100644
--- a/styleguide/python.md
+++ b/styleguide/python.md
@@ -1,5 +1,10 @@
 # Python Style Guidelines [go/cros-pystyle]
 
+*** note
+**Warning: This document is old & has moved.  Please update any links:**<br>
+https://chromium.googlesource.com/chromiumos/docs/+/HEAD/styleguide/python.md
+***
+
 [TOC]
 
 ## Introduction
diff --git a/styleguide/shell.md b/styleguide/shell.md
index 9aeb7ac..c3e7860 100644
--- a/styleguide/shell.md
+++ b/styleguide/shell.md
@@ -1,5 +1,10 @@
 # Shell Style Guidelines [go/cros-shstyle]
 
+*** note
+**Warning: This document is old & has moved.  Please update any links:**<br>
+https://chromium.googlesource.com/chromiumos/docs/+/HEAD/styleguide/shell.md
+***
+
 [TOC]
 
 ## Introduction
diff --git a/test_install_configuration.md b/test_install_configuration.md
index 331e851..9b5d857 100644
--- a/test_install_configuration.md
+++ b/test_install_configuration.md
@@ -1,5 +1,10 @@
 # Configuring Installation and Tests with GN
 
+*** note
+**Warning: This document is old & has moved.  Please update any links:**<br>
+https://chromium.googlesource.com/chromiumos/docs/+/HEAD/test_install_configuration.md
+***
+
 ## Introduction
 
 This guide describes how to configure tests and installation.
diff --git a/testing/fuzzing.md b/testing/fuzzing.md
index d6f29ba..0898ffc 100644
--- a/testing/fuzzing.md
+++ b/testing/fuzzing.md
@@ -1,5 +1,10 @@
 # Fuzz testing in Chrome OS
 
+*** note
+**Warning: This document is old & has moved.  Please update any links:**<br>
+https://chromium.googlesource.com/chromiumos/docs/+/HEAD/testing/fuzzing.md
+***
+
 Fuzzing is a testing technique that feeds auto-generated inputs to a piece of
 target code in an attempt to crash the code. It's one of the most effective tools we
 have for finding [security] and [non-security bugs] (also see
diff --git a/testing/fuzzing_main.md b/testing/fuzzing_main.md
index f80d7a4..c52e672 100644
--- a/testing/fuzzing_main.md
+++ b/testing/fuzzing_main.md
@@ -1,5 +1,10 @@
 # Fuzz testing in Chrome OS
 
+*** note
+**Warning: This document is old & has moved.  Please update any links:**<br>
+https://chromium.googlesource.com/chromiumos/docs/+/HEAD/testing/fuzzing_main.md
+***
+
 [Fuzzing] is a testing technique that feeds auto-generated inputs to a piece
 of target code in an attempt to crash the code. It's one of the most effective
 methods we have for finding [security] and [non-security bugs]
diff --git a/testing/performance.md b/testing/performance.md
index c924426..3cc7e90 100644
--- a/testing/performance.md
+++ b/testing/performance.md
@@ -1,5 +1,10 @@
 # Chrome OS Performance Tests
 
+*** note
+**Warning: This document is old & has moved.  Please update any links:**<br>
+https://chromium.googlesource.com/chromiumos/docs/+/HEAD/testing/performance.md
+***
+
 ## Generating a Bootchart
 
 1.  Enable the bootchart feature when building the image by setting the
diff --git a/testing/python_mock.md b/testing/python_mock.md
index cdb347c..4e5d3bd 100644
--- a/testing/python_mock.md
+++ b/testing/python_mock.md
@@ -1,5 +1,10 @@
 # Python Unittest Mocking
 
+*** note
+**Warning: This document is old & has moved.  Please update any links:**<br>
+https://chromium.googlesource.com/chromiumos/docs/+/HEAD/testing/python_mock.md
+***
+
 The python "mock" library is the preferred mocking library for python unittests
 in the Chromium OS source.  There still exist many tests that use "mox", but
 "mock" is preferred for all new tests.  python-mock is the standard mocking
diff --git a/testing/qemu_unit_tests_design.md b/testing/qemu_unit_tests_design.md
index bc7793a..555bd7e 100644
--- a/testing/qemu_unit_tests_design.md
+++ b/testing/qemu_unit_tests_design.md
@@ -1,5 +1,10 @@
 # Running unittests via QEMU
 
+*** note
+**Warning: This document is old & has moved.  Please update any links:**<br>
+https://chromium.googlesource.com/chromiumos/docs/+/HEAD/testing/qemu_unit_tests_design.md
+***
+
 This doc covers technical details for how we run unittests for non-native
 architectures. It is geared towards people who want a deeper understanding of
 the overall system. If you simply want to execute your tests, see the
diff --git a/testing/running_unit_tests.md b/testing/running_unit_tests.md
index bb34548..21b738f 100644
--- a/testing/running_unit_tests.md
+++ b/testing/running_unit_tests.md
@@ -1,5 +1,10 @@
 # Chromium OS Unit Testing
 
+*** note
+**Warning: This document is old & has moved.  Please update any links:**<br>
+https://chromium.googlesource.com/chromiumos/docs/+/HEAD/testing/running_unit_tests.md
+***
+
 [TOC]
 
 ## Resources for writing unit tests
diff --git a/testing/unit_tests.md b/testing/unit_tests.md
index 8d7840c..f4c9f44 100644
--- a/testing/unit_tests.md
+++ b/testing/unit_tests.md
@@ -1,5 +1,10 @@
 # Best practices for writing Chrome OS unit tests
 
+*** note
+**Warning: This document is old & has moved.  Please update any links:**<br>
+https://chromium.googlesource.com/chromiumos/docs/+/HEAD/testing/unit_tests.md
+***
+
 [Unit tests] verify the correctness of a small piece of source code (e.g. a
 class or function) and live alongside the code they're testing. When a Portage
 package with `src_test` defined in its ebuild file is compiled with a command
diff --git a/tips-and-tricks.md b/tips-and-tricks.md
index ed919a2..1e1c9e7 100644
--- a/tips-and-tricks.md
+++ b/tips-and-tricks.md
@@ -1,5 +1,10 @@
 # Tips And Tricks for Chromium OS Developers
 
+*** note
+**Warning: This document is old & has moved.  Please update any links:**<br>
+https://chromium.googlesource.com/chromiumos/docs/+/HEAD/tips-and-tricks.md
+***
+
 This page contains tips and tricks for developing on Chromium OS.
 
 The free-form content on this page is contributed by developers. Before adding
diff --git a/work_on_branch.md b/work_on_branch.md
index 512751e..8f90910 100644
--- a/work_on_branch.md
+++ b/work_on_branch.md
@@ -1,5 +1,10 @@
 # Chromium OS Guide to Working on Branches
 
+*** note
+**Warning: This document is old & has moved.  Please update any links:**<br>
+https://chromium.googlesource.com/chromiumos/docs/+/HEAD/work_on_branch.md
+***
+
 This guide covers tips to work with branches. You may need to work on release
 branches for Chrome OS versions e.g. `release-R76-12239.B`, or factory and
 stabilize branches that serve a project-specific purpose
diff --git a/write_protection.md b/write_protection.md
index 9994a9b..714638a 100644
--- a/write_protection.md
+++ b/write_protection.md
@@ -1,5 +1,10 @@
 # Write Protection
 
+*** note
+**Warning: This document is old & has moved.  Please update any links:**<br>
+https://chromium.googlesource.com/chromiumos/docs/+/HEAD/write_protection.md
+***
+
 [TOC]
 
 ## Background
diff --git a/xbuddy.md b/xbuddy.md
index 2aa3f59..ebea32d 100644
--- a/xbuddy.md
+++ b/xbuddy.md
@@ -1,5 +1,10 @@
 # xBuddy for Devserver
 
+*** note
+**Warning: This document is old & has moved.  Please update any links:**<br>
+https://chromium.googlesource.com/chromiumos/docs/+/HEAD/xbuddy.md
+***
+
 xBuddy (short for "cros buddy", and "x" is a rotated cross) allows you to obtain
 Chromium OS images or other artifacts off Google Storage and reference locally
 built images. When used with devserver (or scripts that use it), it can also be