update README.md

README.md

@@ -147,7 +147,7 @@ namespace MyCompany.Customizations.Dynamics365.Sales
     {
 ```
 
-> __Note:__ When registering custom implementations of the integration's interfaces, make sure to include the original code found in [/CMSModules/Kentico.Xperience.Dynamics365.Sales/Services/Implementations/](/CMSModules/Kentico.Xperience.Dynamics365.Sales/Services/Implementations/).
+> __Note__ When registering custom implementations of the integration's interfaces, make sure to include the original code found in [/CMSModules/Kentico.Xperience.Dynamics365.Sales/Services/Implementations/](/CMSModules/Kentico.Xperience.Dynamics365.Sales/Services/Implementations/).
 
 The `MapActivityType` method is called while synchronizing activities to determine the name of the Dynamics 365 entity to create, using the passed `activityType` parameter. For example, if you want to create "phonecall" activities in Dynamics 365, but the code name of the activity in Xperience is "phone," your implementation would look something like this:
 
@@ -342,4 +342,4 @@ UPDATE CMS_SettingsKey SET KeyValue = NULL WHERE KeyName LIKE 'dynamics365%'
   - Minimum score (Dynamics365MinScore)
 
   13. Include any other objects from other categories that you've added. You can see [our documentation](https://docs.xperience.io/deploying-websites/exporting-and-importing-sites/exporting-objects) for more information about exporting objects.
-  14. When you're finished selecting export objects, click __Next__ and the export package will be created in the appropriate location and included in the repository.
+  14. When you're finished selecting export objects, click __Next__ and the export package will be created in the appropriate location and included in the repository.