Common practice ≠ good practice. IMX most of the sites that use a 960-grid (or any template grid) are not ones that I would take advice from over the best way to build a website that is fully accessible and usable. As noonnope correctly surmised, I'm not in favour of a fixed width at all, but prefer a fluid layout with min/max constraints. The bottom line is that if you design your site to require a maximised window with no sidebars on a 1024px display to avoid getting horizontal scrollbars then you will be causing problems for a significant minority of visitors, and those problems might include them never even finding the right-most menu item.
I don't see your apostrophe after cameras. Did you already fix it? It was good that Steve pointed it out, although he could have done it in a kinder, gentler way. Sometimes it does take a second pair of eyes to zero in on a mistake.
Nope, the apostrophes are still there in the screenshot, but not used consistently. Sometimes they're there, sometimes they're not.
Another thing that needs to be tightened up is capitalisation. Unlike the apostrophes, you can choose your own house style here, as to whether you want to use capital letters or not. One is not necessarily right and the other wrong (in this context), but you have to be consistent throughout.
This isn't just me being a nasty anal-retentive pedant. People will, consciously or subconsciously, judge the presentation and quality of writing on your site. If it is badly written and has lots of typos, spelling mistakes, missing or erroneous punctuation etc, they are less likely to believe it to be trustworthy. If you're not going to take care over the details when writing the website, why would they trust you to take care over the details of any other aspect of the business? You owe it to your customers and your business to proof-read everything carefully, and to make sure that you haven't got that kind of glaring mistake or inconsistency as the first thing people see. No, the occasional typo is unlikely to turn people away ... but mistakes on that level will lose you business.
That's all very well if you know how wide it needs to be. But in the case of a menu that can have sections added, changed or removed, or one where the text is not set in px and so can be resized, you can easily find situations where what you think ought to be enough width suddenly isn't. A method like Paul's that doesn't rely on knowing the exact dimensions of all its child elements is better, although to have it sticking out potentially beyond the page design and even beyond the viewport is not an ideal solution ... which is why I think the OP is actually trying to solve the wrong problem.