<?xml version="1.0" encoding="UTF-8"?><rss version="2.0"
	xmlns:content="http://purl.org/rss/1.0/modules/content/"
	xmlns:dc="http://purl.org/dc/elements/1.1/"
	xmlns:atom="http://www.w3.org/2005/Atom"
	xmlns:sy="http://purl.org/rss/1.0/modules/syndication/"
		>
<channel>
	<title>Comments on: 11 Steps to Buying the Home Thatâ€™s Right for You &#8211; Step 3: Get Pre-Approved!</title>
	<atom:link href="http://www.lubasf.com/blog/11-steps-to-buying-the-home-that%e2%80%99s-right-for-you-step-3-get-pre-approved.php/feed" rel="self" type="application/rss+xml" />
	<link>http://www.lubasf.com/blog/11-steps-to-buying-the-home-that%e2%80%99s-right-for-you-step-3-get-pre-approved.php</link>
	<description>San Francisco Realtor Reports on San Francisco Real Estate and San Francisco Living</description>
	<lastBuildDate>Wed, 04 May 2011 16:54:18 +0000</lastBuildDate>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
	<generator>http://wordpress.org/?v=3.1.1</generator>
	<item>
		<title>By: Define Your SF Home Buying Needs &#124; Luba's San Francisco Real Estate Blog</title>
		<link>http://www.lubasf.com/blog/11-steps-to-buying-the-home-that%e2%80%99s-right-for-you-step-3-get-pre-approved.php/comment-page-1#comment-174</link>
		<dc:creator>Define Your SF Home Buying Needs &#124; Luba's San Francisco Real Estate Blog</dc:creator>
		<pubDate>Fri, 19 Oct 2007 09:24:43 +0000</pubDate>
		<guid isPermaLink="false">http://www.lubasf.com/blog/11-steps-to-buying-the-home-that%e2%80%99s-right-for-you-step-3-get-pre-approved.php#comment-174</guid>
		<description>[...] So if you&#8217;re following my steps, you are now pre-approved, and know exactly how much home you can afford in San Francisco. [...]</description>
		<content:encoded><![CDATA[<p>[...] So if you&#8217;re following my steps, you are now pre-approved, and know exactly how much home you can afford in San Francisco. [...]</p>
]]></content:encoded>
	</item>
</channel>
</rss>
<!-- WP Super Cache is installed but broken. The path to wp-cache-phase1.php in wp-content/advanced-cache.php must be fixed! -->
