Rename doc/ to docs/

This CL renames doc to docs/ on GitHub, just in case in future we want to expose web pages on GitHub Pages [1]. [1]: https://github.com/blog/2228-simpler-github-pages-publishing BUG= TEST= REF_BUG= REF_CL=130706872 REF_TIME=2016-08-18T18:22:05-07:00 REF_TIME_RAW=1471569725 -0700
google · Aug 19, 2016 · 1c81210 · 1c81210
1 parent a2fe15e
commit 1c81210
Show file tree

Hide file tree

Showing 10 changed files with 6 additions and 6 deletions.
diff --git a/README.md b/README.md
@@ -26,29 +26,29 @@ For historical reasons, the project name *Mozc* has two different meanings:
 
 In this repository, *Mozc* means the second definition unless otherwise noted.
 
-Detailed differences between Google Japanese Input and Mozc are described in [About Branding](doc/about_branding.md).
+Detailed differences between Google Japanese Input and Mozc are described in [About Branding](docs/about_branding.md).
 
 Build Instructions
 ------------------
 
-* [How to build Mozc in Docker](doc/build_mozc_in_docker.md): Android, NaCl, and Linux desktop builds.
-* [How to build Mozc in OS X](doc/build_mozc_in_osx.md): OS X build.
-* [How to build Mozc in Windows](doc/build_mozc_in_windows.md): Windows build.
+* [How to build Mozc in Docker](docs/build_mozc_in_docker.md): Android, NaCl, and Linux desktop builds.
+* [How to build Mozc in OS X](docs/build_mozc_in_osx.md): OS X build.
+* [How to build Mozc in Windows](docs/build_mozc_in_windows.md): Windows build.
 
 Release Plan
 ------------
 
 tl;dr. **There is no stable version.**
 
-As described in [About Branding](doc/about_branding.md) page, Google does
+As described in [About Branding](docs/about_branding.md) page, Google does
 not promise any official QA for OSS Mozc project.  Because of this,
 Mozc does not have a concept of *Stable Release*.  Instead we change version
 number every time when we introduce non-trivial change.  If you are
 interested in packaging Mozc source code, or developing your own products
 based on Mozc, feel free to pick up any version.  They should be equally
 stable (or equally unstable) in terms of no official QA process.
 
-[Release History](doc/release_history.md) page may have additional
+[Release History](docs/release_history.md) page may have additional
 information and useful links about recent changes.
 
 License

diff --git a/doc/about_branding.md → docs/about_branding.md b/doc/about_branding.md → docs/about_branding.md
diff --git a/doc/build_mozc_in_docker.md → docs/build_mozc_in_docker.md b/doc/build_mozc_in_docker.md → docs/build_mozc_in_docker.md
diff --git a/doc/build_mozc_in_osx.md → docs/build_mozc_in_osx.md b/doc/build_mozc_in_osx.md → docs/build_mozc_in_osx.md
diff --git a/doc/build_mozc_in_windows.md → docs/build_mozc_in_windows.md b/doc/build_mozc_in_windows.md → docs/build_mozc_in_windows.md
diff --git a/doc/design_doc/data_protection.md → docs/design_doc/data_protection.md b/doc/design_doc/data_protection.md → docs/design_doc/data_protection.md
diff --git a/doc/design_doc/input_scope.md → docs/design_doc/input_scope.md b/doc/design_doc/input_scope.md → docs/design_doc/input_scope.md
diff --git a/doc/design_doc/mozc_ipc.md → docs/design_doc/mozc_ipc.md b/doc/design_doc/mozc_ipc.md → docs/design_doc/mozc_ipc.md
diff --git a/doc/design_doc/surrounding_text.md → docs/design_doc/surrounding_text.md b/doc/design_doc/surrounding_text.md → docs/design_doc/surrounding_text.md
diff --git a/doc/release_history.md → docs/release_history.md b/doc/release_history.md → docs/release_history.md