Check the Formatting Configuration in your Theme Options Panel. By default, WordPress® comes with several Formatting Filters built into its publishing system. Advanced users may find them annoying, particularly if you already know XHTML and you're not using the Visual Editor for WordPress®. These Formatting Filters include: wpautop, balanceTags, wptexturize, convert_chars & convert_smilies. The most important Filter is wpautop. It converts double line-breaks in your content into paragraphs (<p>...</p>). The other Filters, well, they do a few different things, but for the most part, they're responsible for keeping your code clean, handling XHTML entity conversions for special characters like ampersands, and balancing the overall structure of your code. All of that being said, if you plan to write your own XHTML, without the assistance of the Visual Editor, you can safely disable these Filters to prevent your raw code from being modified by them.
Broken Content: If you've already created Posts/Pages using the Visual Editor for WordPress®, disabling these Filters can cause your existing content to appear broken. For example, the wpautop filter converts double line-breaks in your content into paragraphs (<p>...</p>). So, if you've already published a lot of content that depends on automatic paragraphs, and then you disable wpautop, your content will become jumbled. Just keep this in mind if you disable these Filters, and then find your content in a mess. It is easy to think your theme is to blame, when actually it is just these Filters at work, or not at work. In either case, the problem will be temporary, not permanent. To correct the issue, adjust your configuration. I've attached a screenshot.

PriMoThemes.com is owned & operated by WebSharks, Inc. The WebSharks Framework is a fancy name for what is essentially a core set of PHP, JavaScript and CSS files that have been professionally assembled for the production of high quality themes, plugins and widgets for WordPress®. This framework was crafted with a focus on uniform coding standards, GPL licensing flexibility, and the organization of team-driven efforts within our company and the entire WordPress® community. You can learn more about our framework here.
With any theme, including ours, you can only generalize the CSS styling for widgets. There is no way to pre-determine which widgets you may decide to use. Sometimes, widgets you download from the WordPress.org site will come with their own CSS style sheets or specific rules, and sometimes they will not. The bottom line is that if you decide to use non-standardized widgets ( those not included with WordPress® by default, or with our themes ), then you will need to create your own CSS rules and style them yourself, so they jive with your overall layout. Some widgets will be too wide, others too narrow, and others just look funky. Check the documentation for each widget you're having problems with first, and if all else fails, use your Theme Options Panel to add Custom CSS rules that address your concerns.
No. If you don't want to use FeedBurner®, you can just fill the FeedBurner® options panel with URLs pointing to which ever locations you prefer. That being said, there really is no reason NOT to use FeedBurner®, as it provides additional features not available with WordPress® alone. Such as email subscription capabilities, advanced statistics, syndication methods, PingShot, BuzzBoost, the Awareness API, FeedFlare, their Headline Animator, and the list goes on. FeedBurner® also makes it possible for you to run AdSense® ads within the output of your feed. I've attached a screenshot.

If you know HTML, you'll have no problem writing XHTML, because for all practical purposes, it is the same thing. If you'd like to learn more about the subtle differences between HTML and XHTML, please try this article.
XHTML is an acronym for "Extensible HyperText Markup Language", a reformulation of HTML 4.0 as an XML 1.0 application. It is a family of XML markup languages that mirror or extend versions of the widely used Hypertext Markup Language (HTML), the language that web pages are written in.
While HTML (prior to HTML 5) was defined as an application of Standard Generalized Markup Language (SGML), a very flexible markup language framework, XHTML is an application of XML, a more restrictive subset of SGML. Because XHTML documents need to be well-formed, they can be processed using standard XML tools; unlike HTML, which requires a relatively complex, lenient, and generally custom parser.
You can modify the color scheme easily using the drop-down menu in the Theme Options Panel. So digging through the CSS files should not be needed in most cases. That being said, our themes CAN be tweaked further by qualified web developers. If you'd like some intuitive assistance, please contact PriMoThemes.com for custom development quotes. If you're an aspiring web developer, and you just want to tweak things a little here and there; please check your WordPress® theme directory under: /colors. Depending on which color style you are using, you will need to select a sub-folder from that directory and locate the CSS files for that specific color variation. Also read this article.

Yes, all source files are included. PHP, JavaScript, PNG, PSD, FLA, SWF, etc, etc. We include everything that you might need to make further adjustments. You may find it takes a long time to upload our themes to your server, because ALL of the source files are included. It's also because our themes come with multiple color variations. If you'd like to exclude some of the color variations, you can go into the /colors/ directory, before you upload everything. Feel free to delete the color folders you don't intend to use. The only one that absolutely has to be uploaded, is: /colors/default/, all of the others are optional. Note... you should NEVER exclude /colors/default/. That directory needs to be present at all times. I've attached a screenshot.

Yes. WordPress® allows you to assign Custom Fields to Posts & Pages. This arbitrary extra information is known as meta-data. Our themes create a new panel on both your Post and Page creation forms, titled: Custom Fields Used By This Theme. Please refer to that panel for detailed descriptions about how Custom Fields will be used when they are provided. Most notably, all of our themes understand the thumbnail field, and also the h1_title field. The details about how these fields are used will be made available to you whenever you add or edit content inside WordPress®. I've attached a screenshot.

Yes, it's perfectly OK to remove our credit and copyright notice from the bottom. We've made it very easy for you to do this. Check the Theme Options Panel for the Lower Footbar Companion. You can modify everything in that section easily. I've attached a screenshot.

Yes, absolutely. Not only do they support widgets, all of our themes come bundled with at least three pre-installed / pre-styled widgets. We normally include our own Super Tags widget, the Ad Codes widget, and the Ad Squares widget. While not all of our themes include a Sidebar, we always include at least one widget-ready bar. When there is no Sidebar included, we'll include a Headbar or Footbar, or both. Some themes include all three widget-ready panels.