From 523bc959f5264bdf94f569bfeb447632c9d1e830 Mon Sep 17 00:00:00 2001
From: vuittont60 <81072379+vuittont60@users.noreply.github.com>
Date: Wed, 3 Jan 2024 23:53:56 +0800
Subject: [PATCH] docs: fix typos (#7741)

---
 ci/merge-artifacts.sh                | 2 +-
 docs/contributing-release-process.md | 2 +-
 docs/examples-profiling-vtune.md     | 4 ++--
 3 files changed, 4 insertions(+), 4 deletions(-)

diff --git a/ci/merge-artifacts.sh b/ci/merge-artifacts.sh
index aece95e6c4ad..036911cab523 100755
--- a/ci/merge-artifacts.sh
+++ b/ci/merge-artifacts.sh
@@ -9,7 +9,7 @@
 
 set -ex
 
-# Prepare the upload folder and move all aritfacts that aren't being merged into
+# Prepare the upload folder and move all artifacts that aren't being merged into
 # this folder, e.g. the MSI installer and adapter wasm files.
 rm -rf dist
 mkdir dist
diff --git a/docs/contributing-release-process.md b/docs/contributing-release-process.md
index b25d690567d1..1fa5483d9b06 100644
--- a/docs/contributing-release-process.md
+++ b/docs/contributing-release-process.md
@@ -6,7 +6,7 @@ others might be curious in this as well!
 
 ## Releasing a major version
 
-Major versions of Wasmtime are relased once-a-month. Most of this is automatic
+Major versions of Wasmtime are released once-a-month. Most of this is automatic
 and all that needs to be done is to merge GitHub PRs that CI will
 generate. At a high-level the structure of Wasmtime's release process is:
 
diff --git a/docs/examples-profiling-vtune.md b/docs/examples-profiling-vtune.md
index 61c67d1b572f..9fb45b385865 100644
--- a/docs/examples-profiling-vtune.md
+++ b/docs/examples-profiling-vtune.md
@@ -4,7 +4,7 @@
 and 64-bit x86 architectures. The tool collects profiling data during runtime
 and then, either through the command line or GUI, provides a variety of options
 for viewing and analyzing that data. VTune Profiler is available in both
-commerical and free options. The free, downloadable version is available
+commercial and free options. The free, downloadable version is available
 [here][download] and is backed by a community forum for support. This version is
 appropriate for detailed analysis of your Wasm program.
 
@@ -65,7 +65,7 @@ This command tells the VTune collector (`vtune`) to collect hot spot
 profiling data as Wasmtime is executing `foo.wasm`. The `--profile=vtune` flag enables
 VTune support in Wasmtime so that the collector is also alerted to JIT events
 that take place during runtime. The first time this is run, the result of the
-command is a results diretory `r000hs/` which contains profiling data for
+command is a results directory `r000hs/` which contains profiling data for
 Wasmtime and the execution of `foo.wasm`. This data can then be read and
 displayed via the command line or via the VTune GUI by importing the result.