feat(integrations): fix linting

Author: drobnikj

sources/platform/integrations/workflows-and-notifications/make.md

@@ -53,7 +53,7 @@ Make.com imposes a hard timeout of 5 minutes for synchronous runs. If the Actor
 If you anticipate that the Actor run will exceed 5 minutes, use the asynchronous method with a trigger module instead.
 :::
 
-The primary difference between the two methods is that the synchronous run waits for the Actor or Task to finish and retrieves its output using the "Get Dataset Items" module. By contrast, the asynchronous run watchs for the run of an Actor or task (which could have been triggered from another scenario, manualy from Apify console or elsewhere) and gets its output once it finishes.
+The primary difference between the two methods is that the synchronous run waits for the Actor or Task to finish and retrieves its output using the "Get Dataset Items" module. By contrast, the asynchronous run watches for the run of an Actor or task (which could have been triggered from another scenario, manually from Apify console or elsewhere) and gets its output once it finishes.
 
 ### Synchronous run using the action module
 
@@ -68,7 +68,7 @@ Next, add the Apify module called "Run an Actor" to your scenario and configure
 For this example, we will use the "Google Maps Review Scraper" Actor.
 Make sure to set the "Run synchronously" option to "Yes," so the module waits for the Actor to finish run.
 
-![img_1.png](img_1.png)
+![make-com-sync-2.png](../images/make-com/make-com-sync-2.png)
 
 #### Step 2: Add the Apify "Get Dataset Items" module
 
@@ -77,15 +77,15 @@ In the next step, add the "Get Dataset Items" module to your scenario, which is
 In the "Dataset ID" field, provide the default dataset ID from the Actor run.
 You can find this dataset ID in the variables generated by the previous "Run an Actor" module. If the variables do not appear, run the scenario first, then check again.
 
-![img_2.png](img_2.png)
+![make-com-sync-3.png](../images/make-com/make-com-sync-3.png)
 
 #### Step 3: Add the Google Sheets "Create Spreadsheet Rows" module
 
 Finally, add the Google Sheets "Bulk Add Rows" module to your scenario. This module will automatically create new rows in a Google Sheets file to store the Actor's output.
 
 In the "Spreadsheet ID" field, provide the ID of the target Google Sheets file, which you can find in its URL. Configure the column range (e.g., "A-Z") and map the data retrieved from the "Get Dataset Items" module to the row values.
 
-![img_3.png](img_3.png)
+![make-com-sync-4.png](../images/make-com/make-com-sync-4.png)
 
 You’re all set! Once the scenario is started, it will run the Actor synchronously and export its output to your Google Sheets file.
 
@@ -101,41 +101,41 @@ Next, add the Apify module called "Watch Actor Runs" to your scenario. This modu
 
 For this example, we will use the "Google Maps Review Scraper" Actor.
 
-![img_4.png](img_4.png)
+![make-com-async-1.png](../images/make-com/make-com-async-1.png)
 
 #### Step 2: Add the Apify "Get Dataset Items" module
 
 Add the "Get Dataset Items" module to your scenario to retrieve the output of the Actor run.
 
 In the "Dataset ID" field, provide the default dataset ID from the Actor run. You can find the dataset ID in the variables generated by the "Watch Actor Runs" module.
 
-![img_5.png](img_5.png)
+![make-com-async-2.png](../images/make-com/make-com-async-2.png)
 
 #### Step 3: Add the Google Sheets "Create Spreadsheet Rows" module
 
 Finally, add the Google Sheets "Bulk Add Rows" module to your scenario, which will create new rows in the specified Google Sheets file to store the Actor's output.
 
 In the "Spreadsheet ID" field, enter the ID of the target Google Sheets file, which you can find in its URL. Configure the column range (e.g., "A-Z") and map the data retrieved from the "Get Dataset Items" module to the row values.
 
-![img_6.png](img_6.png)
+![make-com-async-3.png](../images/make-com/make-com-async-3.png)
 
 That’s it! Once the Actor run is complete, its data will be exported to Google Sheets.
 You can initiate the Actor run via the Apify console, a scheduler, or from another Make.com scenario.
 
 ## Available modules and triggers
 
-**Triggers**
+### Triggers
 
-* Watch Actor Runs: Triggers when a selected Actor run is finished.
-* Watch Task Runs: Triggers when a selected task run is finished.
+- Watch Actor Runs: Triggers when a selected Actor run is finished.
+- Watch Task Runs: Triggers when a selected task run is finished.
 
-**Actions**
+### Actions
 
-* Run a task: Runs a selected Actor task.
-* Run an Actor: Runs a selected Actor.
-* Scrape Single URL: Runs a scraper for the website and returns its content as text, markdown and HTML.
-* Make an API Call: Makes an arbitrary authorized API call.
+- Run a task: Runs a selected Actor task.
+- Run an Actor: Runs a selected Actor.
+- Scrape Single URL: Runs a scraper for the website and returns its content as text, markdown and HTML.
+- Make an API Call: Makes an arbitrary authorized API call.
 
-**Searches**
+### Searches
 
-* Get Dataset Items: Retrieves items from a [dataset](/platform/storage/dataset).
+- Get Dataset Items: Retrieves items from a [dataset](/platform/storage/dataset).