UX cleanup on admin settings form

I've been working on a port of Metatag to Backdrop CMS, and I usually like to do a UX pass in the process, contributing suggestions back here too so both projects get a li'l spruce-up. Take or leave the following as you see fit, but here's what I think could be improved about the Metatag settings form (let me know if I misunderstood what these options do)

* Move Custom pager string into advanced settings, remove Additional settings.
* Collapse Internationalization settings fieldset by default
* remove the technical note from the intro paragraph. (Most people using this UI this page won't know what a configuration entity is without a lot more context and explanation than this. This message may likely confuse more than it helps.)

Advanced settings text cleanup:
* Move Load the module's default configurations to the top.
* remove repetitive desc text that doesn't add any value: Control whether the module's default configuration is used. This will not affect configurations exported via Features. (Features module should provide the bit about features, otherwise it will confuse anyone running a site w/o the module who thinks they know what Features are.)
* Change Output meta tags even if only global settings apply to Always output meta tags, even if global default. (the wording "even if only" is very confusing even for native english speakers)
* Change By default Metatag will load the global default values for all pages that do not have meta tags assigned via the normal entity display or via Metatag Context. This may be disabled so that meta tags will only be output on pages that specifically have meta tags configured for them. to When disabled meta tags will only be output where explicitly provided. (very verbose descs are read less often, and often not as clear as being concise)
* Change By default meta tags will not be output on admin pages, but it may be beneficial for some sites to do so. to When disabled, meta tags will not be output on administrative pages. ("by default" is not a useful comparison once the value has been changed.)
* Change Advanced permissions to Add a permission for each individual meta tag (might as well say what this does in the name)
* Remove Optionally add a permission for each individual meta tag. (It's in the label now)
* Change This provides tremendous flexibility for the editorial process, at the expense of making the permissions configuration more tedious. to Provides increased flexibility for the editorial process, but increases complexity in permissions configuration (highs and lows less extreme)
* Change Don't load entity's default language values if no languages match to Only output meta tags that match the requested language
* Remove with the canonical URL pointing to the URL. unless we can define which URL it is pointing to.
* Remove otherwise using defaults. (not sure what that means, if anything)
* Change Don't load entity's default language values if no languages match to Only output meta tags that match the requested language.
* Change On a site with multiple languages it is possible for an entity to not have meta tag values assigned for the language of the current page. By default the meta tags for an entity's default language value will be used in this scenario, with the canonical URL pointing to the URL. This option may be disabled, i.e. to only load meta tags for languages that specifically have them assigned, otherwise using defaults. to When disabled, meta tags for the default language will be output when no match is found for the requested language.
* Change Disabling this will cause all meta tag output to be generated uniquely for each page load to When disabled, all meta tag output will be generated uniquely for each page load
* Change Leave core's meta tags as-is to Always provide canonical, shortlink, and generator meta tags
* Change Drupal core outputs a number of meta tags itself: canonical, shortlink, and generator. Metatag can be used to replace these with custom values. Should Metatag not have values for these meta tags, core's tags will normally be removed. Enabling this option will leave those meta tags on the page, even if Metatag is not replacing them. to When disabled, the meta tags for canonical, shortlink, and generator will be removed if values are not explicitly provided.
* Remove If checked, will ensure that metatag value output is encoded and text filters are processed.. (Not sure this desc provides much value. When/why would you check this box? If sanitization is all it does, that sounds good! Why is it not checked by default?)

Here's a screenshot: