This support document will show you how to "unstick" the posts.

http://en.support.wordpress.com/posts/post-visibility/

I don't quite understand your penultimate paragraph though re. stickies? I don't know what a sticky is...and not sure what you mean when you refer to our 'special' type posts?

I would change the width under #nav to 730px so that the gap at the left and right match and also change the bottom padding there as well to something like 20px so that there is less of a gap between the navigation and the content/sidebar.

#nav {
width: 730px;
padding-bottom: 20px;
}

I would probably do this also so that your sticky posts have a bottom border line like the other posts.

body#home .entry-1, .sticky, body {
border-bottom: 1px solid #000000;
}

I would probably add the following to space the submit button down away from the search box a little.

#searchsubmit {
margin-top: 10px;
}

And maybe this which evens out the right side whitespace to the right of the sidebar with the left side of the content area.

#sidebar {
margin-right: 7px;
}

One other thing. I would use the stick post feature for "special" type posts you want to stick at the top to highlight them, and I typically keep no more than 1 as a sticky, but 2 would be my limit otherwise they lose their "specialness" and just become another post. Right now you have 3 posts as stickies.

I would also shy away from putting symbols into page or post titles such as the heart. Some browsers do not take kindly to symbols and can actually return 404 file not found errors.

#sidebar ul {
margin-bottom: 20px;
margin-top: 0;
}

This puts more space between the widget titles and the bottom of the previous widget and puts a line above the title.

#sidebar h2 {
border-top: 2px solid #000000;
padding-top: 5px;
}

Also, with what I have above, take the border-bottom off in #searchform.

See where that gets you.

It seems that 'border-top' applies to the space between the title (e.g. Categories) and the points (e.g. India/Recipes) - what code would apply to the space ABOVE the title (e.g. 'Categories'/Blogroll')

I think it's looking better and slowly coming together though!

#sidebar ul li {
list-style: none outside none;
margin-bottom: 0;
}

#sidebar ul {
padding-left: 15px;
}

The line between widgets is a little tougher since the theme designer did not include a "widget class or ID. Basically each widget stands alone and the spacing in between is just whatever it is. What you would have to do is to put a section into the CSS for each type of widget and then declare a bottom border and some bottom padding or margin. So, these would be the selectors.

.textwidget

#searchform

#subscribe-blog

.blogroll

Anytime you added a widget, you would have to go back into the CSS and add a section for that particular widget type (archives, recent comments, calendar, etc.).

Is there any way of changing the lay out/style of the widgets on the sidebar? For instance, is it possible to get rid of the big bullet points, and reduce the space between each point? And can we introduce a line inbetween each widget?

#sidebar {
border: medium none;
}

The fonts I see at the moment are much more readable.

How do we get the sidebar so that there is no line border around it?

I think we should probably try changing the font - would you suggest that we go with something bolder? Yeah, we've found that re.the browsers - but apparently, on some it is virtually unreadable due to the blurriness.

The font on the sidebar definitely looks clearer than the rest of the body of text - i definitely should have figured this out by the now, but how do we change the font-colour on the main page?

body#home .entry-1, .sticky, body {
color: #000000;
}

.entry {
font-size: 120%;
}

#sidebar {
color: #000000;
}

Also - I've tried to figure this out, but do you know what part of the code needs to be changed in order to change the font-color on the sidebar?

Thank you!

h1, h2, h3 {
}

No font declaration, just blank.

h1, h2, h3 {
font-family: "josefin-1","josefin-2",sans-serif;
}

For the font size, you are likely going to have to adjust it in several places. This will get you started on the content on the main page and the other static pages.

.entry .entrybody p {
font-size: 120%;
}

For the sidebar, you can do this and it will increase the size of the font in all the sidebar widgets.

#sidebar {
font-size: 120%;
}

See how far that gets you and then we can work on the other bits as necessary. In some themes, you might have to adjust font sizes in multiple places. It just depends on how carried away the theme designer got when doing the design.

You're right re.the typekit font. But I am using the Josefin font through typekit and I have applied it to all areas of the blog, so I still don't really understand why the date is showing up differently.

body {
    font-size: 67%;
}

Bump it up to say 75% and see what you think. That looks pretty good to me.

The font size issue seems to be related to fonts that have been turned out by font factories for use on places like Typekit. Since you have the CSS upgrade, you can just increase the size of the fonts for the particular elements in the page as needed.

What areas/elements do you want to increase the font sizes in?

http://www.google.com/webfonts/family?family=Josefin+Slab&subset=latin#code

Here it uses 'arial', instead of 'rockwell', but it's just doing the same thing. Can't figure out why it's not applying the rule to the date font?

Another question - the font size on our other pages is smaller, how can we uniform this on the css?

Really am sorry for so many questions - if you're fed up, I will find someone else to pester!

h1, h2, h3 {
font-family: "Josefin Slab",Rockwell,serif;
}

but Josefin Slab doesn't seem to be a valid font name, which is why it is moving down the font stack and showing Rockwell instead. Check over at typekit and make sure it exists.

This is probably horribly simple - we've changed our font to josefin, but it won't change the blog post (or date) headers - do you know why this is? We've changed it on typekit and on our css, but it just won't change.

Thanks.