diff --git a/workshop/content/030_basic_content/076_api_faults/020_api_errors/_index.en.md b/workshop/content/030_basic_content/076_api_faults/020_api_errors/_index.en.md
index ebdb77b2..51254de6 100644
--- a/workshop/content/030_basic_content/076_api_faults/020_api_errors/_index.en.md
+++ b/workshop/content/030_basic_content/076_api_faults/020_api_errors/_index.en.md
@@ -135,7 +135,7 @@ In [**FIS**](https://console.aws.amazon.com/fis/home) ensure the experiment is s
 When the experiment begins running issue a new curl request to the `/terminate` path, but this time with a `POST` action.  HTTP `POST` methods are usually used for mutating actions.  
 
 ```bash
-curl -X POST curl ${TERMINATION_URL}
+curl -X POST ${TERMINATION_URL}
 ```
 
 Even with the experiment running you should receive a response that looks similar to
@@ -156,4 +156,4 @@ When the experiment completes after running 3 minutes, you can verify that the i
 
 ## Conclusion 
 
-In this module, we used an SQS queue message to ensure that the TerminateInstances API call would be retried after the fault injection to demonstrate how you can use asynchronous API patterns to mitigate API failures.  
\ No newline at end of file
+In this module, we used an SQS queue message to ensure that the TerminateInstances API call would be retried after the fault injection to demonstrate how you can use asynchronous API patterns to mitigate API failures.