Fix link

Signed-off-by: Alex Ellis (OpenFaaS Ltd) <[email protected]>
openfaas · Aug 13, 2024 · d563aa4 · d563aa4
1 parent 803ab06
commit d563aa4
Showing 1 changed file with 1 addition and 1 deletion.
diff --git a/_posts/2024-08-13-building-functions-via-api-golang.md b/_posts/2024-08-13-building-functions-via-api-golang.md
@@ -22,7 +22,7 @@ Since the Function Builder API has been available, we've mainly seen customers c
 
 **Customer spotlight**
 
-Patchworks (https://www.wearepatchworks.com/) is an iPaaS platform that helps businesses transform and connect data between retail systems such as e-commerce, ERP, Warehouse management and marketplaces. They have a pre-built library of [*Connectors*](https://doc.wearepatchworks.com/product-documentation/connectors-and-instances/connectors-and-instances-introduction#connectors) to sync to/from associated applications, a pre-built library of OpenFaaS hosted scripts, and also allow customers to supply their own code using *[Custom Scripting](https://doc.wearepatchworks.com/product-documentation/developer-hub/custom-scripting)* which supports 6 programming languages via OpenFaaS with others able to be configured in if needed. 
+[Patchworks](https://www.wearepatchworks.com/) is an iPaaS platform that helps businesses transform and connect data between retail systems such as e-commerce, ERP, Warehouse management and marketplaces. They have a pre-built library of [*Connectors*](https://doc.wearepatchworks.com/product-documentation/connectors-and-instances/connectors-and-instances-introduction#connectors) to sync to/from associated applications, a pre-built library of OpenFaaS hosted scripts, and also allow customers to supply their own code using *[Custom Scripting](https://doc.wearepatchworks.com/product-documentation/developer-hub/custom-scripting)* which supports 6 programming languages via OpenFaaS with others able to be configured in if needed. 
 
 Whether the *Custom Script* is pre-supplied by the Patchworks team, or created by a customer, it is built and deployed using the same approach by making a HTTP call to the Function Builder API. The resulting container image is published to a registry, and then gets deployed as an OpenFaaS function. Whenever a script is needed by a user's workflow, it is invoked over HTTP via the OpenFaaS gateway.