Odd issue with content folder on hosted WP install

I am using WP 3.1.3 as offered by our hosting service Aplus.net.

If you do a vanilla install from their control panel it limits the things you can do like add plugins, etc. by putting some of the folders in a “secure” area (I really don’t know what this means). I asked them to move it out of the secure area, which they did.

I am trying to get the Tribulant FAQ plugin to work, and the Tribulant folks told me 2 things:

#1 Where is your wp-config.php file?
#2 Your content folder is called /wordpress-content, not /wp-content as it would be for a standard installation.

In answer to #1 there is the standard vanilla wp-config-sample.php which I copied to wp-config.php.

I see in the WP codex, http://codex.wordpress.org/Editing_wp-config.php that you can put an entry into wp-config.php like this:

Set WP_CONTENT_DIR to the full local path of this directory (no trailing slash), e.g.

define( ‘WP_CONTENT_DIR’, $_SERVER[‘DOCUMENT_ROOT’] . ‘/blog/wp-content’ );

to point to a different content folder. Would this be the recommended fix then?

==================
Underneath all of this I have a remaining question:

Given that my wp-content folder is really named wordpress-content, and I didn’t have a wp-config.php file until a few minutes ago, and it is still just the template file, with none of the valid info filled out, how is it even possible that my WP site works?