summaryrefslogtreecommitdiff
path: root/doc
diff options
context:
space:
mode:
authordosire <sytses@gmail.com>2014-03-10 17:40:40 +0100
committerdosire <sytses@gmail.com>2014-03-10 17:40:40 +0100
commit509c45163a69b608a65f11e3383f565c13d643c4 (patch)
treee243b6b13c64e4abe0bd7f9c65f209a14b6f0a88 /doc
parent0aa389b4911221e0ec5730d5342a1c59f37a8015 (diff)
downloadgitlab-ce-509c45163a69b608a65f11e3383f565c13d643c4.tar.gz
Update references to gitlab dot com.
Diffstat (limited to 'doc')
-rw-r--r--doc/development/architecture.md2
-rw-r--r--doc/install/installation.md2
-rw-r--r--doc/release/security.md2
3 files changed, 3 insertions, 3 deletions
diff --git a/doc/development/architecture.md b/doc/development/architecture.md
index 8a772344b79..ab74af4faf9 100644
--- a/doc/development/architecture.md
+++ b/doc/development/architecture.md
@@ -3,7 +3,7 @@
# Software delivery
-There are two editions of GitLab: [Enterprise Edition](https://www.gitlab.com/features/) (EE) and [Community Edition](http://gitlab.org/gitlab-ce/) (CE).
+There are two editions of GitLab: [Enterprise Edition](https://www.gitlab.com/gitlab-ee/) (EE) and [Community Edition](https://www.gitlab.com/gitlab-ce/) (CE).
GitLab CE is delivered via git from the [gitlabhq repository](https://gitlab.com/gitlab-org/gitlab-ce/tree/master).
New versions of GitLab are released in stable branches and the master branch is for bleeding edge development.
diff --git a/doc/install/installation.md b/doc/install/installation.md
index d6e0a8a0012..16f029dc10f 100644
--- a/doc/install/installation.md
+++ b/doc/install/installation.md
@@ -4,7 +4,7 @@ this should be the highest numbered stable branch (example shown below).
![capture](http://i.imgur.com/d2AlIVj.png)
-If this is unclear check the [GitLab Blog](http://blog.gitlab.org/) for installation guide links by version.
+If this is unclear check the [GitLab Blog](https://www.gitlab.com/blog/) for installation guide links by version.
# Important notes
diff --git a/doc/release/security.md b/doc/release/security.md
index 7ec3991de85..8e5a7e32099 100644
--- a/doc/release/security.md
+++ b/doc/release/security.md
@@ -15,7 +15,7 @@ Please report suspected security vulnerabilities in private to support@gitlab.co
1. Acknowledge the issue to the researcher that disclosed it
1. Fix the issue on a feature branch, do this on the private GitLab development server and update the VERSION and CHANGELOG in this branch
1. Consider creating and testing workarounds
-1. Create feature branches for the blog posts on GitLab.org and GitLab.com and link them from the code branch
+1. Create feature branches for the blog post on GitLab.com and link them from the code branch
1. Merge the code feature branch into master
1. Cherry-pick the code into the latest stable branch
1. Create a git tag vX.X.X for CE and another patch release for EE