From 6c1fc859544d553e5c52e608eaf43934284ff209 Mon Sep 17 00:00:00 2001
From: Dallas <4213800+dallasbrittany@users.noreply.github.com>
Date: Wed, 25 May 2022 11:22:55 -0500
Subject: [PATCH] Update non-rustup-setups.md

---
 docs/src/prerequisites/non-rustup-setups.md | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)

diff --git a/docs/src/prerequisites/non-rustup-setups.md b/docs/src/prerequisites/non-rustup-setups.md
index 5171bdc..be53eb2 100644
--- a/docs/src/prerequisites/non-rustup-setups.md
+++ b/docs/src/prerequisites/non-rustup-setups.md
@@ -1,5 +1,5 @@
 # Non-Rustup setups
-`wasm-pack` compiles your code using the `wasm32-unknown-unknown` target. `wasm-pack` will automatically add this target for Rustup setups if you don't already have it installed by doing `rustup target add wasm32-unknown-unknown`. However, if you're not using Rustup we won't be able to this automatically and you'll have to do this yourself.
+`wasm-pack` compiles your code using the `wasm32-unknown-unknown` target. `wasm-pack` will automatically add this target for Rustup setups if you don't already have it installed by doing `rustup target add wasm32-unknown-unknown`. However, if you're not using Rustup, then we won't be able to do this automatically, and you'll have to do this yourself.
 
 ## Manually add wasm32-unknown-unknown
 *Disclaimer: This is not guaranteed to work for every setup. These instructions below are specific for setups that match the exact rustc release, which means that the downloaded wasm32 target can be incompatible.*