diff --git a/docs/developer-docs/smart-contracts/best-practices/troubleshooting.mdx b/docs/developer-docs/smart-contracts/best-practices/troubleshooting.mdx
index 7a41b31a5a..f49b2967bc 100644
--- a/docs/developer-docs/smart-contracts/best-practices/troubleshooting.mdx
+++ b/docs/developer-docs/smart-contracts/best-practices/troubleshooting.mdx
@@ -22,7 +22,7 @@ On subnets with higher loads, your application may experience elevated latencies
 
 ### Recommendation: Consider moving the canister to another subnet.
 
-If your canister is running on a subnet that has a consistently high load and thus elevated latency, consider adding a [compute allocation](docs/current/developer-docs/gas-cost#execution-and-compute-allocation) setting. A compute allocation of 1% will gauruntee your canister is scheduled for execution once every 100 rounds. 
+If your canister is running on a subnet that has a consistently high load and thus elevated latency, consider adding a [compute allocation](docs/current/developer-docs/gas-cost#execution-and-compute-allocation) setting. A compute allocation of 1% will guarantee your canister is scheduled for execution once every 100 rounds. 
 
 ## Troubleshooting best practices