Please address the comments from this code review:

## Overall Comments
- The indentation style within code blocks is now inconsistent (e.g., the first JS example is fully left-aligned while the later `<script>` block is indented); consider standardizing indentation so the examples are easier to read and visually consistent.
- In the `showPics` example comments, the phrase "second object object" appears twice; it would be clearer to fix this typo to just "second object".
- The `fetch('http://127.0.0.1:3000/airport/00A')` example might be clearer and safer if changed to an HTTPS or relative URL, or explicitly noted as a local-development-only endpoint, to avoid confusion when readers try the example in different environments.

## Individual Comments

### Comment 1
<location path="apit-ajax.md" line_range="159-161" />
<code_context>
-            const images = await response.json();                     // convert the loaded text JSON into a JavaScript object / array
-            
-            const name = images[1].name;     // the 'name' property of the second object in the 'images' array
-            const description = images[1].description; // 'description' property of the second object object in the 'images' array
-            const address = images[1].address; // 'address' property of the second object object in the 'images' array
+    // simplified example without error handling
+    async function showPics() {
</code_context>
<issue_to_address>
**issue (typo):** Fix the repeated word "object" in these comments.

Both comments currently say "second object object"; update them to "second object".

```suggestion
            const name = images[1].name;     // the 'name' property of the second object in the 'images' array
            const description = images[1].description; // 'description' property of the second object in the 'images' array
            const address = images[1].address; // 'address' property of the second object in the 'images' array
```
</issue_to_address>

### Comment 2
<location path="apit-ajax.md" line_range="221" />
<code_context>
 </script>
 ```
+
 `fetch()` and `json()` functions both return a promise. Hence, you need use the await keyword to wait for the promise to be fulfilled. In this case that means that the data has been loaded.


</code_context>
<issue_to_address>
**issue (typo):** Add a missing "to" in "need use" for correct grammar.

Update the sentence to: "you need to use the await keyword."

```suggestion
`fetch()` and `json()` functions both return a promise. Hence, you need to use the await keyword to wait for the promise to be fulfilled. In this case that means that the data has been loaded.
```
</issue_to_address>

### Comment 3
<location path="apit-ajax.md" line_range="177" />
<code_context>

 In newer versions of JavaScript, promise is increasingly used instead of [callback functions](extras.md#callback-functions-and-callback-hell). A promise is an object that ‘promises’ to return value.
 The advantages of the promise are e.g. simpler syntax and easier error handling. For example, to submit a form using the fetch method:
+
</code_context>
<issue_to_address>
**issue (typo):** Add an article before "value" for grammatical correctness.

Change “promises to return value” to “promises to return a value” (or “some value”) for more natural English.

```suggestion
In newer versions of JavaScript, promise is increasingly used instead of [callback functions](extras.md#callback-functions-and-callback-hell). A promise is an object that ‘promises’ to return a value.
```
</issue_to_address>