If you do not enter data into the fields, they will not be shown at all. If you want to enter data manny fieldset, for example address and phone numbers, you can set the visibility to unlisted. With that set, those fieldsets will not be displayed.
As for the warning issued by Codestyling Localization, that can be ignored. Connections uses many strings which are translated by WordPress, so Connections will use them instead of requiring translators to translate the text again just for Connections. It also keeps resource useage down since multiple translations for the same string do not need to be loaded in the memory at the same time.
Opps… I did read the message clearly, I thought it was complaining about multiple text domains…
Any way, that message can be ignored as well. Connections does call the
load_textdomain function, but only to load custom translations a user may have created for Connections. If custom translation does not exist, then it does call the
load_plugin_textdomain function. This is a more advanced setup that provides more flexibility by allowing custom translations that are update safe. There is no danger of some filters and action not being run with the way this is setup.
Hope that helps!