aboutsummaryrefslogtreecommitdiffstats
path: root/docs/releasing.html
diff options
context:
space:
mode:
authorEric Engestrom <[email protected]>2017-02-26 23:58:03 +0000
committerEric Engestrom <[email protected]>2017-02-27 14:15:10 +0000
commit077879cf5e6b90023fb495e36d05bb9d0960bbd0 (patch)
treef0dc7d184de89112279699079b3519492cdd198c /docs/releasing.html
parent7f268cf12b39d1de8ff38cf5beea50298cf841c2 (diff)
docs: fix a few typos
Noticed a couple, found the rest using vimspell. Signed-off-by: Eric Engestrom <[email protected]> Reviewed-by: Emil Velikov <[email protected]>
Diffstat (limited to 'docs/releasing.html')
-rw-r--r--docs/releasing.html8
1 files changed, 4 insertions, 4 deletions
diff --git a/docs/releasing.html b/docs/releasing.html
index 242881a70bc..07d459581cb 100644
--- a/docs/releasing.html
+++ b/docs/releasing.html
@@ -57,11 +57,11 @@ to a minimum.
<h2>Feature releases</h2>
<ul>
-<li>Available approximatelly every three months.
+<li>Available approximately every three months.
<li>Initial timeplan available 2-4 weeks before the planned branchpoint (rc1)
on the mesa-announce@ mailing list.
<li>A <a href="#prerelease">pre-release</a> announcement should be available
-approximatelly 24 hours before the final (non-rc) release.
+approximately 24 hours before the final (non-rc) release.
</ul>
<h2>Stable releases</h2>
@@ -69,7 +69,7 @@ approximatelly 24 hours before the final (non-rc) release.
<li>Normally available once every two weeks.
<li>Only the latest branch has releases. See note below.
<li>A <a href="#prerelease">pre-release</a> announcement should be available
-approximatelly 48 hours before the actual release.
+approximately 48 hours before the actual release.
</ul>
<p>
@@ -453,7 +453,7 @@ and SSH passphrase(s) to sign and upload the files, respectively.
<h3>Add the sha256sums to the release notes</h3>
<p>
-Edit docs/relnotes/X.Y.Z.html to add the sha256sums as availabe in the mesa-X.Y.Z.announce template. Commit this change.
+Edit docs/relnotes/X.Y.Z.html to add the sha256sums as available in the mesa-X.Y.Z.announce template. Commit this change.
</p>
<h3>Back on mesa master, add the new release notes into the tree</h3>