Update typereferences-element.md (#1767)

* Update typereferences-element.md

* Update chart-(obsolete).md

Author: todorarabadzhiev

doc-output/configure-the-report-engine/typereferences-element.md

@@ -1,7 +1,7 @@
 ---
-title: TypeReferences Element
-page_title: TypeReferences Element Configuration
-description: "Learn how to set up the TypeReferences Element, allowing you to use custom user functions in the report and create ObjectDataSource components."
+title: typeReferences Element
+page_title: typeReferences Element Configuration
+description: "Learn how to set up the typeReferences Element, allowing you to use custom user functions in the report and create ObjectDataSource components."
 slug: telerikreporting/using-reports-in-applications/export-and-configure/configure-the-report-engine/typeReferences-element
 tags: typeReferences, element, user, function, ObjectDataSource
 published: True
@@ -21,7 +21,7 @@ table th:nth-of-type(2) {
 
 >note This element was first introduced in the [2024 Q1 (18.0.24.305)](https://www.telerik.com/support/whats-new/reporting/release-history/progress-telerik-reporting-2024-q1-(18-0-24-305)) Reporting version.
 
-Defines a collection of type references used by the Reporting Engine to resolve the custom types permitted to be used during the design and processing stages. The assemblies used by the types in TypeReferences section are loaded into application domain if the type is successfully resolved, so it's not necessary to declare the assembly also in the AssemblyReferences section.
+Defines a collection of type references used by the Reporting Engine to resolve the custom types permitted to be used during the design and processing stages. The assemblies used by the types in the typeReferences section are loaded into the application domain if the type is successfully resolved, so it's not necessary to declare the assembly also in the AssemblyReferences section.
 
 XML-based configuration file:
 
@@ -36,7 +36,7 @@ XML-based configuration file:
 JSON-based configuration file:
 
 ````JSON
-"TypeReferences": [
+"typeReferences": [
 ],
 ````
 
@@ -46,11 +46,11 @@ The following sections describe attributes, child elements, and parent elements.
 
 |   |   |
 | ------ | ------ |
-|Attributes|<ul><li>__typeName__ – mandatory string attribute. Specifies the full name of the type, i.e. namespace and class name.</li><li>__assemblyName__ – mandatory string attribute. Specifies the name of the assembly that contains the type.</li><li>__publicKeyToken__ – optional string attribute. Specifies the public key token of the assembly. Can be omitted or can have empty or null value.</li></ul>|
+|Attributes|<ul><li>__typeName__ – mandatory string attribute. Specifies the full name of the type, i.e., namespace and class name.</li><li>__assemblyName__ – mandatory string attribute. Specifies the name of the assembly that contains the type.</li><li>__publicKeyToken__ – optional string attribute. Specifies the public key token of the assembly. Can be omitted or can have an empty or null value.</li></ul>|
 |Child Elements|<ul><li>__add__ - Optional element. Adds a type reference to the collection.</li><li>__clear__ - Optional element. Removes all references to inherited type names, allowing only the references that are added by the current add element.</li><li>__remove__ - Optional element. Removes a reference to an inherited type name from the collection.</li></ul>|
 |Parent Elements|<ul><li>__configuration__ - Specifies the root element in every configuration file that is used by the common language runtime and the .NET Framework applications.</li><li>__Telerik.Reporting__ - Configures all settings that Telerik Reporting Engine uses.</li></ul>|
 
-When providing the Public Key Token, the Reporting Engine will try to match it with the Public Key Token of the found DLL. It will not load an assembly with the same name and a different Public Key Token and will throw an exception instead. If the Public Key Token is omitted in the configuration, the Reporting Engine will load the first DLL, which name matches the provided Assembly Name. Potentially, this may allow bad agents to replace trusted assemblies with malicious ones and constitutes a security vulnerability. Since the Public Key Token provides an extra security layer to your application, we advise to always include it in the configuration file.
+When providing the Public Key Token, the Reporting Engine will try to match it with the Public Key Token of the found DLL. It will not load an assembly with the same name and a different Public Key Token and will throw an exception instead. If the Public Key Token is omitted in the configuration, the Reporting Engine will load the first DLL, whose name matches the provided Assembly Name. Potentially, this may allow bad agents to replace trusted assemblies with malicious ones and constitutes a security vulnerability. Since the Public Key Token provides an extra security layer to your application, we advise always including it in the configuration file.
 
 ## Example
 
@@ -77,7 +77,7 @@ JSON-based configuration file:
 
 ````JSON
 "telerikReporting": {
-	"TypeReferences": [
+	"typeReferences": [
 		{
 			"typeName": "MyNamespace.MyClassName",
 			"assemblyName": "MyAssemblyName",
@@ -87,7 +87,7 @@ JSON-based configuration file:
 }
 ````
 
-> When adding the `Telerik.Reporting` section manually, do not forget to register it in `configSections` element of the configuration file. Failing to do so will result in a [ConfigurationErrorsException](https://learn.microsoft.com/en-us/dotnet/api/system.configuration.configurationerrorsexception?view=dotnet-plat-ext-7.0) with the following text: *Configuration system failed to initialize*.
+> When adding the `Telerik.Reporting` section manually, do not forget to register it in the `configSections` element of the configuration file. Failing to do so will result in a [ConfigurationErrorsException](https://learn.microsoft.com/en-us/dotnet/api/system.configuration.configurationerrorsexception?view=dotnet-plat-ext-7.0) with the following text: *Configuration system failed to initialize*.
 
 ## See Also
 

report-items/chart-(obsolete).md

@@ -14,6 +14,7 @@ previous_url: /report-items-chart, /featuressplineareas
 >* The Chart report item is now superseded by the more advanced [Graph]({%slug telerikreporting/designing-reports/report-structure/graph/overview%}) report item. The Graph is most often used for building powerful OLAP and Pivot charts. 
 >* The Chart report item is not supported in .NET Core projects and in projects deployed on Azure. 
 >* The complete Chart report item documentation is available as a `CHM` file up to Telerik Reporting version 8.2.14.1204, and can be downloaded from [your Telerik account](https://www.telerik.com/account/downloads/product-download?product=REPORTING).
+>* If your reports utilize the Chart item, you need to add a [typeReference]({%slug telerikreporting/using-reports-in-applications/export-and-configure/configure-the-report-engine/typeReferences-element%}) in your configuration to explicitly allow the element to be processed: `<add typeName="Telerik.Reporting.Processing.Chart" assemblyName="Telerik.Reporting" publicKeyToken="a9d7983dfcc261be" />`. This is required due to vulnerabilities in the item code.
 
 The Chart report item is used to display a chart on a report.