Add titles to codeblocks and switch from diff codeblock to language codeblock

Signed-off-by: Paul Schultz <pschultz@pobox.com>

docs/integrations/azure/discovery.md

@@ -32,8 +32,7 @@ Setup [Azure integration](locations.md) with `host` and `token`. Host must be `d
 
 At your configuration, you add one or more provider configs:
 
-```yaml
-# app-config.yaml
+```yaml title="app-config.yaml"
 catalog:
   providers:
     azureDevOps:
@@ -94,39 +93,45 @@ yarn add --cwd packages/backend @backstage/plugin-catalog-backend-module-azure
 
 Once you've done that, you'll also need to add the segment below to `packages/backend/src/plugins/catalog.ts`:
 
-```diff
-/* packages/backend/src/plugins/catalog.ts */
-+import { AzureDevOpsEntityProvider } from '@backstage/plugin-catalog-backend-module-azure';
+```ts title="packages/backend/src/plugins/catalog.ts"
+/* highlight-add-next-line */
+import { AzureDevOpsEntityProvider } from '@backstage/plugin-catalog-backend-module-azure';
 
 const builder = await CatalogBuilder.create(env);
 /** ... other processors and/or providers ... */
-+builder.addEntityProvider(
-+  AzureDevOpsEntityProvider.fromConfig(env.config, {
-+    logger: env.logger,
-+    // optional: alternatively, use scheduler with schedule defined in app-config.yaml
-+    schedule: env.scheduler.createScheduledTaskRunner({
-+      frequency: { minutes: 30 },
-+      timeout: { minutes: 3 },
-+    }),
-+    // optional: alternatively, use schedule
-+    scheduler: env.scheduler,
-+  }),
-+);
+/* highlight-add-start */
+builder.addEntityProvider(
+  AzureDevOpsEntityProvider.fromConfig(env.config, {
+    logger: env.logger,
+    // optional: alternatively, use scheduler with schedule defined in app-config.yaml
+    schedule: env.scheduler.createScheduledTaskRunner({
+      frequency: { minutes: 30 },
+      timeout: { minutes: 3 },
+    }),
+    // optional: alternatively, use schedule
+    scheduler: env.scheduler,
+  }),
+);
+/* highlight-add-end */
 ```
 
 ## Alternative Processor
 
 As an alternative to the entity provider `AzureDevOpsEntityProvider`, you can still use the `AzureDevopsDiscoveryProcessor`.
 
-```diff
-// In packages/backend/src/plugins/catalog.ts
-+import { AzureDevOpsDiscoveryProcessor } from '@backstage/plugin-catalog-backend-module-azure';
+```ts title="packages/backend/src/plugins/catalog.ts"
+/* highlight-add-next-line */
+import { AzureDevOpsDiscoveryProcessor } from '@backstage/plugin-catalog-backend-module-azure';
 
- export default async function createPlugin(
-   env: PluginEnvironment,
- ): Promise<Router> {
-   const builder = await CatalogBuilder.create(env);
-+  builder.addProcessor(AzureDevOpsDiscoveryProcessor.fromConfig(env.config, { logger: env.logger }));
+export default async function createPlugin(
+  env: PluginEnvironment,
+): Promise<Router> {
+  const builder = await CatalogBuilder.create(env);
+  /* highlight-add-next-line */
+  builder.addProcessor(AzureDevOpsDiscoveryProcessor.fromConfig(env.config, { logger: env.logger }));
+
+  // ..
+}
 ```
 
 ```yaml

docs/integrations/azure/org.md

@@ -21,7 +21,7 @@ yarn add --cwd packages/backend @backstage/plugin-catalog-backend-module-msgraph
 
 Next add the basic configuration to `app-config.yaml`
 
-```yaml
+```yaml title="app-config.yaml"
 catalog:
   providers:
     microsoftGraphOrg:
@@ -39,25 +39,30 @@ catalog:
 Finally, register the plugin in `catalog.ts`.
 For large organizations, this plugin can take a long time, so be careful setting low frequency / timeouts.
 
-```diff
- // packages/backend/src/plugins/catalog.ts
-+import { MicrosoftGraphOrgEntityProvider } from '@backstage/plugin-catalog-backend-module-msgraph';
+```ts title="packages/backend/src/plugins/catalog.ts"
+/* highlight-add-next-line */
+import { MicrosoftGraphOrgEntityProvider } from '@backstage/plugin-catalog-backend-module-msgraph';
 
- export default async function createPlugin(
+export default async function createPlugin(
    env: PluginEnvironment,
- ): Promise<Router> {
-   const builder = await CatalogBuilder.create(env);
+): Promise<Router> {
+  const builder = await CatalogBuilder.create(env);
 
-+  builder.addEntityProvider(
-+    MicrosoftGraphOrgEntityProvider.fromConfig(env.config, {
-+      logger: env.logger,
-+      schedule: env.scheduler.createScheduledTaskRunner({
-+        frequency: { hours: 1 },
-+        timeout: { minutes: 50 },
-+        initialDelay: { seconds: 15}
-+      }),
-+    }),
-+  );
+  /* highlight-add-start */
+  builder.addEntityProvider(
+    MicrosoftGraphOrgEntityProvider.fromConfig(env.config, {
+      logger: env.logger,
+      schedule: env.scheduler.createScheduledTaskRunner({
+        frequency: { hours: 1 },
+        timeout: { minutes: 50 },
+        initialDelay: { seconds: 15}
+      }),
+    }),
+  );
+  /* highlight-add-end */
+
+  // ..
+}
 ```
 
 ## Authenticating with Microsoft Graph
@@ -71,7 +76,7 @@ If you can't do this, you'll have to create an App Registration.
 
 ### App Registration
 
-If none of the other authentication methods work, you can create an app registration in the azure portal.  
+If none of the other authentication methods work, you can create an app registration in the azure portal.
 By default the graph plugin requires the following Application permissions (not Delegated) for Microsoft Graph:
 
 - `GroupMember.Read.All`
@@ -150,15 +155,17 @@ Entities can also be excluded from backstage by returning `undefined`.
 
 These Transformers are be registered when configuring `MicrosoftGraphOrgEntityProvider`
 
-```diff
- builder.addEntityProvider(
-   MicrosoftGraphOrgEntityProvider.fromConfig(env.config, {
-     // ...
-+    groupTransformer: myGroupTransformer,
-+    userTransformer: myUserTransformer,
-+    organizationTransformer: myOrganizationTransformer,
-   }),
- );
+```ts
+builder.addEntityProvider(
+  MicrosoftGraphOrgEntityProvider.fromConfig(env.config, {
+    // ...
+    /* highlight-add-start */
+    groupTransformer: myGroupTransformer,
+    userTransformer: myUserTransformer,
+    organizationTransformer: myOrganizationTransformer,
+    /* highlight-add-end */
+  }),
+);
 ```
 
 When using custom transformers, you may want to customize the data returned.
@@ -243,7 +250,7 @@ Try importing a smaller set of data (e.g. `filter: displayName eq 'John Smith'`)
 
 See [Troubleshooting Azure Identity Authentication Issues](https://aka.ms/azsdk/js/identity/troubleshoot)
 
-### Error while reading users from Microsoft Graph: Authorization_RequestDenied - Insufficient privileges to complete the operation.
+### Error while reading users from Microsoft Graph: Authorization_RequestDenied - Insufficient privileges to complete the operation
 
 - Make sure you've granted all the required permissions to your application registration or managed identity
 - Make sure the permissions are `Application` permissions rather than `Delegated`