random spelling

usync/01.uSync/20.guides/20.content.md

@@ -2,10 +2,10 @@
 title: Turn Off Content Edition
 ---
 
-Starting with Umbraco v9, Content edition is enabled by default. This means all changes to content and media will be saved to disk, in the uSync folder.
+Starting with Umbraco v9, Content Edition is enabled by default. This means all changes to content and media will be saved to disk, in the uSync folder.
 
 ## Disable Content Saving to Disk. 
-if you want to stop uSync from saving content to disk you can turn this off, by telling uSync to only Save Settings on Save:
+If you want to stop uSync from saving content to disk you can turn this off by telling uSync to only Save Settings on Save:
 
 ```json title="appsettings.json"
 {

usync/01.uSync/20.guides/30.dictionary.md

@@ -4,7 +4,7 @@ title: Dictionary Handler
 
 
 ## Change the DictionaryHandler's Group
-By default the DictionaryHandler is treated as a content handler, so Dictionary items are synced when you sync content. 
+By default, the DictionaryHandler is treated as a content handler, so Dictionary items are synced when you sync content. 
 
 It might be that you want your Dictionary items to be synced as settings and this can be done by changing the group the DictionaryHandler is assigned to. 
 
@@ -25,7 +25,7 @@ It might be that you want your Dictionary items to be synced as settings and thi
 ```
 
 ## Make the Dictionary Handler "Create" only
-You may also want to configure the dictionary handler so it only syncs new entries and leaves existing items that your users might have entered alone, you can configure the handler to be 'CreateOnly' so it will only sync new items:
+You may also want to configure the Dictionary Handler so it only syncs new entries and leaves existing items that your users might have entered alone, you can configure the handler to be 'CreateOnly' so it will only sync new items:
 
 
 ```json title=appsettings.json 

usync/01.uSync/20.guides/40.guid.md

@@ -18,7 +18,7 @@ This file structure makes it easy for you to identify and navigate changes to th
 However, there are times when using the file names can cause issues. When you have content items with very long names or you rename a lot of items you can end up with quite a few 'marker' files on disk from when the name was changed. 
 
 ## Guid File Names Setting
-To simplify this and circumvent path length issues, you can instruct uSync to use the GUID ID of an item as the filename, this is done by setting the `GuidNames` value on the handler set. 
+To simplify this and circumvent path length issues, you can instruct uSync to use the GUID ID of an item as the filename. This is done by setting the `GuidNames` value on the handler set. 
 
 The default value for this setting is **false.**
 

usync/02.complete/03.guides/02.Exporter/02.exporter.md

@@ -18,7 +18,7 @@ When creating an export, you will be presented with several options.
 ## Dependencies
 When you include an item in an export via Exporter you will be presented with the option to include dependencies. 
 
-When dependencies are included, Exporter will calculate the items and settings required to fully import something to another Umbraco installation. These will include doctypes, datatypes, templates, and any other elements needed. 
+When dependencies are included, Exporter will calculate the items and settings required to fully import to another Umbraco installation. This will include doctypes, datatypes, templates, and any other elements needed. 
 
 ## Include Media Files
 If selected, the export will also include any physical media required to import a media item. 

usync/02.complete/03.guides/05.ResPoint.md

@@ -16,7 +16,7 @@ Initially restore points will be stored in the sites `/uSync/restore` folder but
 
 #### Cloud Based Restore Points
 
-By default restore points are saved in the `uSync/Restore` folder of your site. This will be fine for a lot of situations, but if for some reason it isn't you can put them somewhere else. 
+By default restore points are saved in the `uSync/Restore` folder of your site. This will be fine for a lot of situations, but if for some reason it isn't, you can put them somewhere else. 
 
 Therefore, the uSync.Complete.Restore.Azure package allows you to put the restore point into azure from config.
 

usync/02.complete/04.extending/00.overview.md

@@ -12,7 +12,7 @@ uSync.Complete builds upon the core uSync package, so you can still use value ma
 [uSync Value Mappers](../../uSync/extending/valuemappers)
 
 ## Syncing Items 
-if you have your own items stored outside of existing Umbraco objects and you want them to sync you will need to write your own SyncHandler and SyncSerializers to handle the serialization and deserialization of the items. 
+If you have your own items stored outside of existing Umbraco objects and you want them to sync you will need to write your own SyncHandler and SyncSerializers to handle the serialization and deserialization of the items. 
 
 [The Vendr.uSync package is a good example of how you can extend uSync to include your own Serializers and Handlers](https://github.com/vendrhub/vendr-usync/tree/v2/dev/src/Vendr.uSync)