Fix for blank lines around code fences (#38255)

content/apps/creating-github-apps/authenticating-with-a-github-app/authenticating-as-a-github-app.md

@@ -47,6 +47,7 @@ You can use {% data variables.product.company_short %}'s Octokit.js SDK to authe
    ```javascript copy
    import { App } from "octokit";
    ```
+
 1. Create a new instance of `App`. In the following example, replace `APP_ID` with a reference to your app's ID. Replace `PRIVATE_KEY` with a reference to the value of your app's private key.
 
    ```javascript copy

content/apps/creating-github-apps/authenticating-with-a-github-app/managing-private-keys-for-github-apps.md

@@ -46,9 +46,11 @@ To verify a private key:
 
    ![Screenshot of a private key in a {% data variables.product.prodname_github_app %} settings page. The fingerprint, the part of the private key after the colon, is outlined in dark orange.](/assets/images/github-apps/github-apps-private-key-fingerprint.png)
 1. Generate the fingerprint of your private key (PEM) locally by using the following command:
+
     ```shell
     openssl rsa -in PATH_TO_PEM_FILE -pubout -outform DER | openssl sha256 -binary | openssl base64
     ```
+
 1. Compare the results of the locally generated fingerprint to the fingerprint you see in {% data variables.product.product_name %}.
 
 ## Deleting private keys

content/apps/creating-github-apps/writing-code-for-a-github-app/creating-ci-tests-with-the-checks-api.md

@@ -57,6 +57,7 @@ You'll use the [Ruby programming language](https://www.ruby-lang.org/en/), the [
 You don't need to be an expert in any of these tools or concepts to complete this project. This guide will walk you through all the required steps. Before you begin creating CI tests with the Checks API, you'll need to do the following:
 
 1. Clone the [Creating CI tests with the Checks API](https://github.com/github-developer/creating-ci-tests-with-the-checks-api) repository.
+
    ```shell
    git clone https://github.com/github-developer/creating-ci-tests-with-the-checks-api.git
    ```

content/apps/creating-github-apps/writing-code-for-a-github-app/setting-up-your-development-environment-to-create-a-github-app.md

@@ -407,6 +407,7 @@ Here are a few common problems and some suggested solutions. If you run into any
     **A:** You may not be running the Smee client, running the Smee command with the wrong parameters or you may not have the correct Smee domain in your GitHub App settings. First check to make sure the Smee client is running in a Terminal tab. If that's not the problem, visit your [app settings page](https://github.com/settings/apps) and check the fields shown in "[Step 2. Register a new GitHub App](#step-2-register-a-new-github-app)." Make sure the domain in those fields matches the domain you used in your `smee -u <unique_channel>` command in "[Step 1. Start a new Smee channel](#step-1-start-a-new-smee-channel)." If none of the above work, check that you are running the full Smee command including the `--path` and `--port` options, for example: `smee --url https://smee.io/qrfeVRbFbffd6vD --path /event_handler --port 3000` (replacing `https://smee.io/qrfeVRbFbffd6vD` with your own Smee domain).
 
 - **Q:** I'm getting an `Octokit::NotFound` 404 error in my debug output:
+
     ```
     2018-12-06 15:00:56 - Octokit::NotFound - POST {% data variables.product.api_url_code %}/app/installations/500991/access_tokens: 404 - Not Found // See: /v3/apps/#create-a-new-installation-token:
     ```