Changes in 44f348c: Updated Customizing Izenda Settings (markdown)

				Integration/Tutorials/Customizing-Izenda-Settings.md
			
          @@ -96,7 +96,7 @@ For more a more detailed code sample, click any of the headings.

           ##How do I add custom code?

          -To enable a custom configuration, we must put the key and connection string in the ``InitializeReporting()`` method. **If settings have already been set on the **Settings.aspx** page, they should be removed and set via code in the global.asax- otherwise, there could be complications when initializing. When adding custom code for a production integration, we recommend disabling **Settings.aspx** and **Izenda.config** altogether to prevent any conflicts from occurring.** Here is the process flow for enabling custom code: 

          +To enable a custom configuration, we must put the key and connection string in the ``InitializeReporting()`` method. **If settings have already been set on the Settings.aspx page, they should be removed and set via code in the global.asax- otherwise, there could be complications when initializing. When adding custom code for a production integration, we recommend disabling Settings.aspx and Izenda.config altogether to prevent any conflicts from occurring.** Here is the process flow for enabling custom code: 

             * Navigate via the file system to the root directory of your Izenda Reports installation

             * Open your global.asax file in a text editor or your favorite IDE

...	...	@@ -96,7 +96,7 @@ For more a more detailed code sample, click any of the headings.
96	96
97	97	##How do I add custom code?
98	98
99		-To enable a custom configuration, we must put the key and connection string in the ``InitializeReporting()`` method. If settings have already been set on the Settings.aspx page, they should be removed and set via code in the global.asax- otherwise, there could be complications when initializing. When adding custom code for a production integration, we recommend disabling Settings.aspx and Izenda.config altogether to prevent any conflicts from occurring. Here is the process flow for enabling custom code:
	99	+To enable a custom configuration, we must put the key and connection string in the ``InitializeReporting()`` method. If settings have already been set on the Settings.aspx page, they should be removed and set via code in the global.asax- otherwise, there could be complications when initializing. When adding custom code for a production integration, we recommend disabling Settings.aspx and Izenda.config altogether to prevent any conflicts from occurring. Here is the process flow for enabling custom code:
100	100
101	101	* Navigate via the file system to the root directory of your Izenda Reports installation
102	102	* Open your global.asax file in a text editor or your favorite IDE