Guides/Izenda-AdHoc-Driver.md
... ...
@@ -101,7 +101,7 @@ Configuring the Izenda Fusion Driver consists of several steps:
101 101
102 102
####1. Create the Fusion Driver
103 103
104
-At first you should create FusionDriver object and set up it as default driver for the Izenda AdHoc. Here is example how to do it in C#:
104
+At first you should create a FusionDriver object and set up it as default driver for the Izenda AdHoc. Here is example how to do it in C#:
105 105
106 106
```csharp
107 107
FusionDriver fusionDriver = new FusionDriver();
... ...
@@ -173,7 +173,7 @@ fd.AddConstraint("OD2/Account.Id", "OD2/User.AccountID");
173 173
174 174
#####c) Saving Reports with Fusion
175 175
176
-When using indirect database connections and saving your reports to the FileSystem is not an option, you can use the SavedReportsDriver setting to specify a direct link to a database where you can store your reports. The following example sets up the connection string to the database that contains the reports table. If you store reports in the file system then skip this step(use FileSystemAdHocConfig if you do this).
176
+When using indirect database connections and saving your reports to the FileSystem is not an option, you can use the SavedReportsDriver setting to specify a direct link to a database where you can store your reports. The following example sets up the connection string to the database that contains the reports table. If you store reports in the file system then skip this step (Use FileSystemAdHocConfig if you do this).
177 177
178 178
```csharp
179 179
((DatabaseAdHocConfig)AdHocSettings.AdHocConfig).SavedReportsDriver = new MSSQLDriver("your_mssql_direct_database_connection_string");
... ...
@@ -181,7 +181,7 @@ When using indirect database connections and saving your reports to the FileSyst
181 181
182 182
#####d) Set up cache
183 183
184
-Getting data from several data source providers may take a lot of time and resources when many connections are added. This will result in a slow connection to the providers due to large amount of data being transferred, etc. That’s why the cache is enabled by default for the Izenda Fusion Driver. By default, cache expiration time is set to 12PM on Saturday. This means that every Saturday, the cache will be cleared and all data will be requested from the providers during the next session.
184
+Getting data from several data source providers may take a lot of time and resources when many connections are added. This will result in a slow connection to the providers due to large amount of the data being transferred, etc. That’s why the cache is enabled by default for the Izenda Fusion Driver. By default, cache expiration time is set to 12PM on Saturday. This means that every Saturday, the cache will be cleared and all data will be requested from the providers during the next session.
185 185
186 186
You can configure the cache yourself by using the following properties and methods:
187 187