Decouple menu location strings again

[SergeyBiryukov]

[32806] brought back the string I removed in [31941] and [31951]:

$description   = '<p>' . sprintf( _n( 'Your theme contains %s menu location. Select which menu you would like to use.', 'Your theme contains %s menu locations. Select which menu appears in each location.', $num_locations ), number_format_i18n( $num_locations ) );

Should be replaced with:

if ( 1 == $num_locations ) {
	$description   = '<p>' . __( 'Your theme supports one menu. Select which menu you would like to use.' );
} else {
	$description   = '<p>' . sprintf( _n( 'Your theme supports %s menu. Select which menu appears in each location.', 'Your theme supports %s menus. Select which menu appears in each location.', $num_locations ), number_format_i18n( $num_locations ) );
}

[SergeyBiryukov]

In 33741:

Customizer: Use existing decoupled strings in Menu Locations section. See [31941] and [31951].

props egill.
fixes #33416.

[pavelevap]

@SergeyBiryukov: Sorry for off-topic, but why it is "Menu Location" in Customizer when it is "Theme Location" on Menu page? It should be the same for consistency, I guess?

[SergeyBiryukov]

Replying to pavelevap:

@SergeyBiryukov: Sorry for off-topic, but why it is "Menu Location" in Customizer when it is "Theme Location" on Menu page? It should be the same for consistency, I guess?

Good catch, looks like it's also not very consistent in different parts of code. Let's create a new ticket for that.

[pavelevap]

Done: #33743