about summary refs log tree commit diff
diff options
context:
space:
mode:
authorbors <bors@rust-lang.org>2021-11-13 11:17:38 +0000
committerbors <bors@rust-lang.org>2021-11-13 11:17:38 +0000
commitf51fb341dd3ff79f400ee816dceb81eb2d0c5106 (patch)
treef53b9d0e28947c0046213198ae7d6e9eb0a07fc4
parentcc9d7fff8fa11665e16823e28140e681c495fc39 (diff)
parent1df10f0c6230fe6f3cadf8274779bc7d369885f5 (diff)
downloadrust-f51fb341dd3ff79f400ee816dceb81eb2d0c5106.tar.gz
rust-f51fb341dd3ff79f400ee816dceb81eb2d0c5106.zip
Auto merge of #7969 - togami2864:fix-typo, r=xFrednet
fix typo

just fixed typo

changelog: none
-rw-r--r--doc/changelog_update.md2
1 files changed, 1 insertions, 1 deletions
diff --git a/doc/changelog_update.md b/doc/changelog_update.md
index 115848c4804..0cbad2c0924 100644
--- a/doc/changelog_update.md
+++ b/doc/changelog_update.md
@@ -32,7 +32,7 @@ bullet points might be helpful:
   need to check out the Rust release tag of the stable release.
   [Link][rust_stable_tools]
 
-Usually you want to wirte the changelog of the **upcoming stable release**. Make
+Usually you want to write the changelog of the **upcoming stable release**. Make
 sure though, that `beta` was already branched in the Rust repository.
 
 To find the commit hash, issue the following command when in a `rust-lang/rust` checkout: