summaryrefslogtreecommitdiff
path: root/doc/release
diff options
context:
space:
mode:
authorEwan Edwards <eedwards@perforce.com>2015-02-03 15:18:40 -0800
committerEwan Edwards <eedwards@perforce.com>2015-02-03 15:18:40 -0800
commitad6c372eeee5d112ad199dd4e487df584976445d (patch)
tree802124a688c9d90861c033a23342512008a56665 /doc/release
parente6e337088bbb4736983119928b6b6b451bd3ef20 (diff)
downloadgitlab-ce-ad6c372eeee5d112ad199dd4e487df584976445d.tar.gz
Fix a number of discovered typos, capitalization of developer and
product names, plus a couple of instances of bad Markdown markup.
Diffstat (limited to 'doc/release')
-rw-r--r--doc/release/howto_rc1.md2
-rw-r--r--doc/release/monthly.md2
2 files changed, 2 insertions, 2 deletions
diff --git a/doc/release/howto_rc1.md b/doc/release/howto_rc1.md
index 25923d16f34..e8e8c8a821d 100644
--- a/doc/release/howto_rc1.md
+++ b/doc/release/howto_rc1.md
@@ -104,7 +104,7 @@ bundle exec rake release["x.x.0.rc1"]
```
Now developers can use master for merging new features.
-So you should use stable branch for future code chages related to release.
+So you should use stable branch for future code changes related to release.
### 5. Release GitLab CI RC1
diff --git a/doc/release/monthly.md b/doc/release/monthly.md
index 175112b90c6..4297bc7e2b7 100644
--- a/doc/release/monthly.md
+++ b/doc/release/monthly.md
@@ -207,7 +207,7 @@ __3. Tweet to blog__
Send out a tweet to share the good news with the world.
List the most important features and link to the blog post.
-Proposed tweet "Release of GitLab X.X & CI Y.Y! FEATURE, FEATURE and FEATURE <link-to-blogpost> #gitlab"
+Proposed tweet "Release of GitLab X.X & CI Y.Y! FEATURE, FEATURE and FEATURE &lt;link-to-blog-post&gt; #gitlab"
Consider creating a post on Hacker News.