Update naming convention in CSX and documentation.

Author: sarahelsaig

README.md

@@ -48,8 +48,8 @@ Specifies a path to a C# script file that can define further project processors.
 
 When executing the plugins, all _OrchardCoreContrib.PoExtractor_ assemblies are automatically loaded, and two globals are defined:
 
-- `List<IProjectProcessor> projectProcessors`: Add an instance of your custom `IProjectProcessor` implementation type to this list.
-- `List<string> projectFiles`: In the unlikely case that you have to add a new project file type (such as _.fsproj_) add the project file paths to this list.
+- `List<IProjectProcessor> ProjectProcessors`: Add an instance of your custom `IProjectProcessor` implementation type to this list.
+- `List<string> ProjectFiles`: In the unlikely case that you have to add a new project file type (such as _.fsproj_) add the project file paths to this list.
 
 > [!TIP]
 > You can't import NuGet packages in your script file, but you can import local DLL files using the `#r "path/to/package.dll"` directive. The path can be relative to the script file's location so you can import packages from the build directory of the project you are extracting from. This can be especially useful if you launch the tool as using MSBuild as a post-build action. (For remote scripts loaded with a URL, the path can be relative to the current working directory.) For example:

test/OrchardCoreContrib.PoExtractor.Tests/PluginTestFiles/BasicJsonLocalizationProcessor.csx

@@ -74,4 +74,4 @@ public class BasicJsonLocalizationProcessor : IProjectProcessor
     }
 }
 
-projectProcessors.Add(new BasicJsonLocalizationProcessor());
+ProjectProcessors.Add(new BasicJsonLocalizationProcessor());