Merge pull request #564 from zapier/targetUrl-fix

PLATSUPP-988 - Update hook-trigger.md

docs/_build/triggers/hook-trigger.md

@@ -61,9 +61,9 @@ Zapier includes a `targetUrl` when making this request. You need to store the ta
 
 Your app's event system would determine which stored subscriptions should be invoked when an event occurs in your app, posting to the corresponding stored `targetUrl`.
 
-The webhook URL can be accessed via  `{{bundle.targetUrl}}`.
+The webhook URL can be accessed via  {% raw %}`{{bundle.targetUrl}}`{% endraw %}.
 
-For example, for Gitlab's API `url` is used as the key for the `{{bundle.targetUrl}}` value that contains the webhook URL to send data to.
+For example, for Gitlab's API `url` is used as the key for the {% raw %}`{{bundle.targetUrl}}`{% endraw %} value that contains the webhook URL to send data to.
 
 ![](https://cdn.zappy.app/8b7941e3092850bd7edf331cb78b5659.png)
 
@@ -113,4 +113,4 @@ To test the REST Hook trigger, [build a Zap in the editor](https://platform.zapi
 
 ## 5. Define your output
 
-Define sample data and output fields following [the guide](https://platform.zapier.com/build/sample-data).
+Define sample data and output fields following [the guide](https://platform.zapier.com/build/sample-data).