From 23fa5d7d9e0ccb3663f4c714efa6c48593dbd449 Mon Sep 17 00:00:00 2001
From: Jacob Vosmaer <contact@jacobvosmaer.nl>
Date: Tue, 22 Sep 2015 13:44:43 +0200
Subject: [PATCH] Fix typo

---
 doc/migrate_ci_to_ce/README.md | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)

diff --git a/doc/migrate_ci_to_ce/README.md b/doc/migrate_ci_to_ce/README.md
index 83fd447ff07..ab69f0fde7e 100644
--- a/doc/migrate_ci_to_ce/README.md
+++ b/doc/migrate_ci_to_ce/README.md
@@ -79,7 +79,7 @@ sudo -u git -H bundle exec rake gitlab:env:info RAILS_ENV=production
 
 - (3) Decide where to store CI build traces on GitLab server. GitLab CI uses
   files on disk to store CI build traces. The default path for these build
-traces is `/var/opt/gitlab/gitlab-ci/build` (Omnibus) or
+traces is `/var/opt/gitlab/gitlab-ci/builds` (Omnibus) or
 `/home/git/gitlab/builds` (Source). If you are storing your repository data in
 a special location, or if you are using NFS, you should make sure that you
 store build traces on the same storage as your Git repositories.