layout docs fixed

Author: dotnetprog

Guide-XrmToolBox.md

@@ -11,12 +11,12 @@ This tool was created to support more data types that the official tool does.
 ### Upcoming features 🔜
 🔜 Supports for multiselect optionset \
 🔜 ~~Configuration Data Importation~~ $${\color{red}This \space is \space no \space longer \space planned.}$$ \
-🔜 ~~Configuration Data Exportation~~  <span style="color:red">This is no longer planned.</span>
+🔜 ~~Configuration Data Exportation~~ $${\color{red}This \space is \space no \space longer \space planned.}$$
 
 > [!IMPORTANT]  
-> Data import/export features will only be available through the cli tool.  \
-> Since the cli tool is made with .Net Core and XTB Plugins is in .Net Framework, It's really hard to keep a sharable codebase and retricts the usage of some modern libraries.  \
-> CLI tool documentation [here](https://github.com/dotnetprog/dataverse-configuration-migration-tool)
+> - Data import/export features will only be available through the cli tool.  \
+> - Since the cli tool is made with .Net Core and XTB Plugins is in .Net Framework, It's really hard to keep a sharable codebase and retricts the usage of some modern libraries.  \
+> - CLI tool documentation [here](https://github.com/dotnetprog/dataverse-configuration-migration-tool)
 
 
 ##  What's a schema definition file exactly 🤔❓

README.md

@@ -5,9 +5,9 @@ This repository contains a custom .NET CLI tool designed to export and import co
 ### Download latest release
 Get latest version of the tool built on this [release](https://github.com/dotnetprog/dataverse-configuration-migration-tool/releases/latest)
 > [!NOTE]  
-> Interactive Login is now available with the CLI tool. The use of service principal is no more mandatory but still recommanded for automation scenarios. \
-> To automate the use of the tool, let's say within a pipeline (e.g Github Action,Azure Devops Pipeline),`appsettings.Production.json` will need to be setup manually with your azure service principal credentials.  \
-> [Quick Guide](https://recursion.no/blogs/dataverse-setup-service-principal-access-for-environment/) to create an azure service principal
+> - Interactive Login is now available with the CLI tool. The use of service principal is no more mandatory but still recommanded for automation scenarios. \
+> - To automate the use of the tool, let's say within a pipeline (e.g Github Action,Azure Devops Pipeline),`appsettings.Production.json` will need to be setup manually with your azure service principal credentials.  \
+> - [Quick Guide](https://recursion.no/blogs/dataverse-setup-service-principal-access-for-environment/) to create an azure service principal
 ## Why ❓
 
 Configuration Migration Tool and the PowerPlatform Cli Tool (pac data import verb) seem to have it's limitations when automating in ci/cd. Also, these two only works on a windows machine. \
@@ -131,11 +131,11 @@ Dataverse.ConfigurationMigrationTool.Console.exe export-data --schema "C:\temp\d
 ```
 
 > [!TIP]
-> To use service principal credentials, the interactive login flag `--il` or `-il` must be omitted. \
-> If you use the executable directly, you must edit the `appsettings.Production.json` file with your service principal credentials \
-> If you use `dotnet run`, you can set the secrets using `dotnet user-secrets` as shown above or edit the `appsettings.Development.json` file. \
-> you can also set environment variables `Dataverse__ClientId`, `Dataverse__ClientSecret` and `Dataverse__Url` to override the settings in the json files. \
-> you can also use these commandline arguments `--Dataverse:ClientId`, `--Dataverse:ClientSecret` and `--Dataverse:Url` to override the settings in the json files.
+> - To use service principal credentials, the interactive login flag `--il` or `-il` must be omitted. \
+> - If you use the executable directly, you must edit the `appsettings.Production.json` file with your service principal credentials \
+> - If you use `dotnet run`, you can set the secrets using `dotnet user-secrets` as shown above or edit the `appsettings.Development.json` file. \
+> - you can also set environment variables `Dataverse__ClientId`, `Dataverse__ClientSecret` and `Dataverse__Url` to override the settings in the json files. \
+> - you can also use these commandline arguments `--Dataverse:ClientId`, `--Dataverse:ClientSecret` and `--Dataverse:Url` to override the settings in the json files.
 
 ## 🤝 Contributing 🤝