Notes on the guide:
"Custom Localization Keys"
Should probably call this "Overriding Content Localization Keys" and move it below the "Substitutions" heading.
Language.GetText is not recommended unless you don't want auto registration of the key, so it shouldn't be in that spot
Should have a link to the "Custom Fields" section below (see <link> for how to add extra localizations to your content, beyond the default properties provided by tML)
"Substitutions"
I've been thinking it would be nice to do some sort of scoping/relative pathing for key references. Should be easy. That way you'd just need Common.SomeSharedTooltip for eg
"Adding Content"
Should have a mention to the above proposed added section about how to define your own localization keys in code to be exported to the files (and the need to retrieve them at least once during load)
"Prefix"
Should probably be a common heading "Translation File Names". With the requirements for pathing
List of supported cultures
Does it have to be in Localization/ or just recommended?
The default file path (is this one created when making a sample mod with the mod generator?)
Link to the "Adding a new Language" section
"Custom Keys"
Suggest rename to "Manually Adding Keys" and adding a code snippet
"Custom Fields"
Suggest rename to "Adding Localizable Properties"
Explain more about GetOrRegisterLocalization and equivalent methods on Language
Mention that the LocalizedText instance should be retrieved at least once during mod load time in order for it to be registered for export to the translation files
The main example for "Elsewhere in the code" should be using the property (since you have the instance accessible anyway)
Main.NewText(SwitchingToMessage.Value)
A separate example can illustrate use of GetLocalizationKey and the other extension methods, but note that you would only use them if the parameter string was dynamic
Maybe paste some example code from ExampleChest
A note that this. is required to access these methods on your own type (sadly)
"ModType and ILocalizedModType"
Should probably go with the "Adding Localizable Properties" section ^
"Adding a new Language"
Easier instruction is to just copy one of the english files and rename the culture.
Needs a section explaining how you're meant to work with these files, and that there's no point adding comments or altering the structure of them, because they inherit comments and structure from the english files.
What exactly does happen if someone splits up their english translations. Will the other languages auto-split up to match?
What if someone alters the comments in the english file?
What if a key is removed from english file?