fix: fix search and replace error in language markers

Author: honzajavorek

sources/academy/platform/deploying_your_code/input_schema.md

@@ -19,7 +19,7 @@ Though writing an [input schema](/platform/actors/development/actor-definition/i
 
 In the root of our project, we'll create a file named **INPUT_SCHEMA.json** and start writing the first part of the schema.
 
-```javascripton
+```json
 {
     "title": "Adding actor input",
     "description": "Add all values in list of numbers with an arbitrary length.",
@@ -34,7 +34,7 @@ The **title** and **description** simply describe what the input schema is for,
 
 In order to define all of the properties our actor is expecting, we must include them within an object with a key of **properties**.
 
-```javascripton
+```json
 {
     "title": "Adding actor input",
     "description": "Add all values in list of numbers with an arbitrary length.",
@@ -55,7 +55,7 @@ Each property's key corresponds to the name we're expecting within our code, whi
 
 Within our new **numbers** property, there are two more fields we must specify. Firstly, we must let the platform know that we're expecting an array of numbers with the **type** field. Then, we should also instruct Apify on which UI component to render for this input property. In our case, we have an array of numbers, which means we should use the **json** editor type that we discovered in the ["array" section](/platform/actors/development/actor-definition/input-schema#array) of the input schema documentation. We could also use **stringList**, but then we'd have to parse out the numbers from the strings.
 
-```javascripton
+```json
 {
     "title": "Adding actor input",
     "description": "Add all values in list of numbers with an arbitrary length.",
@@ -76,7 +76,7 @@ Within our new **numbers** property, there are two more fields we must specify.
 
 The great thing about building an input schema is that it will automatically validate your inputs based on their type, maximum value, minimum value, etc. Sometimes, you want to ensure that the user will always provide input for certain fields, as they are crucial to the actor's run. This can be done by using the **required** field and passing in the names of the fields you'd like to require.
 
-```javascripton
+```json
 {
     "title": "Adding actor input",
     "description": "Add all values in list of numbers with an arbitrary length.",

sources/academy/platform/deploying_your_code/inputs_outputs.md

@@ -59,7 +59,7 @@ If we run this right now, we'll see **null** in our terminal - this is because w
 
 We'll now add an **INPUT.json** file within **storage/key_value_stores/default** to match what we're expecting in our code.
 
-```javascripton
+```json
 {
     "numbers": [5, 5, 5, 5]
 }
@@ -213,7 +213,7 @@ Since we've changed our code a lot from the way it originally was by wrapping it
 
 After running our script, there should be a single item in the default dataset that looks like this:
 
-```javascripton
+```json
 {
     "solution": 20
 }

sources/academy/platform/deploying_your_code/output_schema.md

@@ -25,7 +25,7 @@ Firstly, create a `.actor` folder in the root of your actor's source code. Then,
 
 Next, copy-paste the following template code into your `actor.json` file.
 
-```javascripton
+```json
 {
     "actorSpecification": 1,
     "name": "___ENTER_ACTOR_NAME____",
@@ -73,7 +73,7 @@ To configure the output schema, simply replace the fields in the template with t
 
 For reference, you can use the [Zappos Scraper source code](https://github.com/PerVillalva/zappos-scraper-actor/blob/main/.actor/actor.json) as an example of how the final implementation of the output tab should look in a live actor.
 
-```javascripton
+```json
 {
     "actorSpecification": 1,
     "name": "zappos-scraper",

sources/academy/platform/expert_scraping_with_apify/apify_api_and_client.md

@@ -39,7 +39,7 @@ Though it's a bit unintuitive, this is a perfect activity for learning how to us
 
 The new actor should take the following input values, which be mapped to parameters in the API calls:
 
-```javascripton
+```json
 {
     // How much memory to allocate to the Amazon actor
     // Must be a power of 2

sources/academy/platform/expert_scraping_with_apify/migrations_maintaining_state.md

@@ -35,7 +35,7 @@ Before moving forward, read about actor [events](/sdk/js/docs/upgrading/upgradin
 
 Once again returning to our Amazon **demo-actor**, let's say that we need to store an object in memory (as a variable) containing all of the scraped ASINs as keys and the number of offers scraped from each ASIN as values. The object should follow this format:
 
-```javascripton
+```json
 {
     "B079ZJ1BPR": 3,
     "B07D4R4258": 21

sources/academy/platform/expert_scraping_with_apify/saving_useful_stats.md

@@ -36,7 +36,7 @@ Before moving on, give these valuable resources a quick lookover:
 
 In our Amazon actor, each dataset result must now have the following extra keys:
 
-```javascripton
+```json
 {
     "dateHandled": "date-here", // the date + time at which the request was handled
     "numberOfRetries": 4, // the number of retries of the request before running successfully
@@ -46,7 +46,7 @@ In our Amazon actor, each dataset result must now have the following extra keys:
 
 Also, an object including these values should be persisted during the run in th Key-Value store and logged to the console every 10 seconds:
 
-```javascripton
+```json
 {
     "errors": { // all of the errors for every request path
         "some-site.com/products/123": [

sources/academy/platform/expert_scraping_with_apify/solutions/integrating_webhooks.md

@@ -102,7 +102,7 @@ await Actor.exit();
 
 Cool! But **wait**, don't forget to configure the **INPUT_SCHEMA.json** file as well! It's not necessary to do this step, as we'll be calling the actor through Apify's API within a webhook, but it's still good to get into the habit of writing quality input schemas that describe the input values your actors are expecting.
 
-```javascripton
+```json
 {
     "title": "Amazon Filter Actor",
     "type": "object",

sources/academy/platform/expert_scraping_with_apify/solutions/using_api_and_client.md

@@ -130,7 +130,7 @@ else await withAPI();
 
 And before we push to the platform, let's not forget to write an input schema in the **INPUT_SCHEMA.JSON** file:
 
-```javascripton
+```json
 {
   "title": "Actor Caller",
   "type": "object",

sources/academy/platform/getting_started/inputs_outputs.md

@@ -42,7 +42,7 @@ Then, replace everything in **INPUT_SCHEMA.json**  with this:
 
 > This step isn't necessary, as the actor will still be able to take input in JSON format without it; however, we are providing the content for this actor's input schema in this lesson, as it will give the Apify platform a blueprint off of which it can generate a nice UI for your inputs, as well as validate their values.
 
-```javascripton
+```json
 {
     "title": "Number adder",
     "type": "object",

sources/academy/tutorials/apify_scrapers/getting_started.md

@@ -118,7 +118,7 @@ https://apify.com/store
 
 We also need to somehow distinguish the **Start URL** from all the other URLs that the scraper will add later. To do this, click the **Details** button in the **Start URL** form and see the **User data** input. Here you can add any information you'll need during the scrape in a JSON format. For now, just add a label to the **Start URL**.
 
-```javascripton
+```json
 {
   "label": "START"
 }
@@ -182,7 +182,7 @@ This is because even though it matches our **Pseudo URL**'s format, the HTML ele
 
 Let's use the above **Pseudo URL** in our task. We should also add a label as we did with our **Start URL**. This label will be added to all pages that were enqueued into the request queue using the given **Pseudo URL**.
 
-```javascripton
+```json
 {
   "label": "DETAIL"
 }