[Documentation] Switch Step 2 to fenced

docs/src/tutorials/index.md

@@ -2488,9 +2488,10 @@ server. Our first step will be to add a service that will handle interactions
 with the server; this will not be used by Open MCT directly, but will be 
 used by subsequent components we add.
 
-    /*global define,WebSocket*/
+```diff
+/*global define,WebSocket*/
 
-    define(
+define(
     [],
     function () {
         "use strict";
@@ -2524,7 +2525,8 @@ used by subsequent components we add.
 
         return ExampleTelemetryServerAdapter;
     }
-    );
+);
+```
 __tutorials/telemetry/src/ExampleTelemetryServerAdapter.js__
 
 When created, this service initiates a connection to the server, and begins 
@@ -2541,9 +2543,10 @@ subsystems. This means that we need to convert the data from the dictionary
 into domain object models, and expose these to Open MCT via a 
 `modelService`.
 
-    /*global define*/
+```diff
+/*global define*/
 
-    define(
+define(
     function () {
         "use strict";
 
@@ -2620,7 +2623,8 @@ into domain object models, and expose these to Open MCT via a
 
         return ExampleTelemetryModelProvider;
     }
-    );
+);
+```
 __tutorials/telemetry/src/ExampleTelemetryModelProvider.js__
 
 This script implements a `provider` for `modelService`; the `modelService` is a 
@@ -2673,9 +2677,10 @@ This allows our telemetry dictionary to be expressed as domain object models
 fix this, we will need another script which will add these subsystems to the 
 root-level object we added in Step 1.
 
-    /*global define*/
+```diff
+/*global define*/
 
-    define(
+define(
     function () {
         "use strict";
 
@@ -2721,7 +2726,8 @@ root-level object we added in Step 1.
 
         return ExampleTelemetryInitializer;
     }
-    );
+);
+```
 __tutorials/telemetry/src/ExampleTelemetryInitializer.js__
 
 At the conclusion of Step 1, the top-level My Spacecraft object was empty. This