GITBOOK-26: Fixed code format

Author: eshanrnh

15/umbraco-cms/reference/security/two-factor-authentication.md

@@ -204,7 +204,6 @@ Umbraco controls how the UI is for user login and user edits, but will still nee
 In the following example, we will use the [GoogleAuthenticator NuGet Package](https://www.nuget.org/packages/GoogleAuthenticator/). Despite the name, this package works for both Google and Microsoft authenticator apps. It can be used to generate the QR code needed to activate the app for the website.
 
 {% code title="TwoFactorAuthInfo.cs" lineNumbers="true" %}
-
 ```csharp
 using System.Runtime.Serialization;
 using Google.Authenticator;
@@ -289,15 +288,13 @@ public class UmbracoUserAppAuthenticator : ITwoFactorProvider
     public bool ValidateTwoFactorSetup(string secret, string token) => ValidateTwoFactorPIN(secret, token);
 }
 ```
-
 {% endcode %}
 
 First, we create a model with the information required to set up the 2FA provider. Then we implement the `ITwoFactorProvider` with the use of the `TwoFactorAuthenticator` from the GoogleAuthenticator NuGet package.
 
 Now we need to register the `UmbracoUserAppAuthenticator` implementation and the view to show to set up this provider. This can be done on the `IUmbracoBuilder` in your startup or a composer.
 
 {% code title="UmbracoAppAuthenticatorComposer.cs" lineNumbers="true" %}
-
 ```csharp
 using Umbraco.Cms.Core.Composing;
 using Umbraco.Cms.Core.Security;
@@ -314,13 +311,11 @@ public class UmbracoAppAuthenticatorComposer : IComposer
  }
 }
 ```
-
 {% endcode %}
 
 The last thing required is to register the provider in the Backoffice client so that the user can enable it. This can be done in a `umbraco-package.json` file.
 
-{% code title="~/App_Plugins/TwoFactorProviders/umbraco-package.json" lineNumbers="true" %
-}
+{% code title="~/App_Plugins/TwoFactorProviders/umbraco-package.json" lineNumbers="true" %}
 ```json
 {
   "$schema": "../../umbraco-package-schema.json",
@@ -339,7 +334,6 @@ The last thing required is to register the provider in the Backoffice client so
   ]
 }
 ```
-
 {% endcode %}
 
 At this point, the 2FA is active, but no users have set up 2FA yet.
@@ -392,7 +386,7 @@ The 2FA experience can be customized in Umbraco. This can be done by creating a
 
 The following examples show how to customize the 2FA activation screen and the 2FA login screen.
 
-The examples are using the [Lit](https://lit.dev/) library to create custom elements. This is the recommended way of creating custom elements in Umbraco. Lit is a light-weight library that augments the [Custom Elements API](https://developer.mozilla.org/en-US/docs/Web/API/Web\_components/Using\_custom\_elements) to provide a declarative, performant, and interoperable way to create web components.
+The examples are using the [Lit](https://lit.dev/) library to create custom elements. This is the recommended way of creating custom elements in Umbraco. Lit is a light-weight library that augments the [Custom Elements API](https://developer.mozilla.org/en-US/docs/Web/API/Web_components/Using_custom_elements) to provide a declarative, performant, and interoperable way to create web components.
 
 The examples are using the `@umbraco-cms/backoffice` package to get access to the Umbraco backoffice components and services. This package is included in Umbraco and can be used to create custom elements that look and feel like the rest of the Umbraco backoffice.
 
@@ -405,7 +399,6 @@ The 2FA activation screen can be customized. This should be done if you have a 2
 To customize the 2FA activation screen, you need to create a JavaScript module. The module should export a default custom element to be used in the activation screen. This module should be placed in the `App_Plugins/TwoFactorProviders` folder.
 
 {% code title="~/App_Plugins/TwoFactorProviders/2fa-activation.js" lineNumbers="true" %}
-
 ```javascript
 import { UserService } from '@umbraco-cms/backoffice/external/backend-api';
 import { css, html } from '@umbraco-cms/backoffice/external/lit';
@@ -613,15 +606,13 @@ export default class My2faActivationElement extends UmbLitElement {
 
 customElements.define('my-2fa-activation', My2faActivationElement);
 ```
-
 {% endcode %}
 
 This module will show a QR code and an input field for the user to enter the code from the authenticator app. When the user submits the form, the code will be sent to the server to validate. If the code is correct, the provider will be enabled.
 
 To replace the default activation screen with the custom view, you need to register the element in the `umbraco-package.json` file that you created before. The final form of the file should look like this:
 
 {% code title="~/App_Plugins/TwoFactorProviders/umbraco-package.json" lineNumbers="true" %}
-
 ```json
 {
   "$schema": "../../umbraco-package-schema.json",
@@ -641,7 +632,6 @@ To replace the default activation screen with the custom view, you need to regis
   ]
 }
 ```
-
 {% endcode %}
 
 ### Customizing the login screen
@@ -660,7 +650,7 @@ You can use the following code as a starting point. This will give you a view lo
 
 ![Custom 2FA login](images/2fa-login-custom-view.png)
 
-The following code is an example of a custom 2FA login screen using [Lit](https://lit.dev/). This is the recommended way of creating a custom 2FA login screen. Lit is a light-weight library that augments the [Custom Elements API](https://developer.mozilla.org/en-US/docs/Web/API/Web\_components/Using\_custom\_elements) to provide a declarative, performant, and interoperable way to create web components.
+The following code is an example of a custom 2FA login screen using [Lit](https://lit.dev/). This is the recommended way of creating a custom 2FA login screen. Lit is a light-weight library that augments the [Custom Elements API](https://developer.mozilla.org/en-US/docs/Web/API/Web_components/Using_custom_elements) to provide a declarative, performant, and interoperable way to create web components.
 
 The element registers two properties: providers and returnPath. These properties are used to render the view. The providers property is an array of strings, where each string is the name of a 2FA provider. The returnPath is the path to redirect to after a successful login. Both supplied by the login screen automatically.