<?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: Drafting Errors in the Bear Stearns Merger Agreement? What a Shock!</title>
	<atom:link href="http://www.adamsdrafting.com/2008/03/24/drafting-errors-bear-stearns/feed/" rel="self" type="application/rss+xml" />
	<link>http://www.adamsdrafting.com/2008/03/24/drafting-errors-bear-stearns/</link>
	<description></description>
	<lastBuildDate>Tue, 16 Mar 2010 21:26:31 +0000</lastBuildDate>
	<generator>http://wordpress.org/?v=2.9.2</generator>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
		<item>
		<title>By: Mergers &#38; Acquisitions &#171; Kandeski Creative</title>
		<link>http://www.adamsdrafting.com/2008/03/24/drafting-errors-bear-stearns/comment-page-1/#comment-49183</link>
		<dc:creator>Mergers &#38; Acquisitions &#171; Kandeski Creative</dc:creator>
		<pubDate>Sun, 06 Apr 2008 05:41:46 +0000</pubDate>
		<guid isPermaLink="false">http://www.adamsdrafting.com/2008/03/24/drafting-errors-bear-stearns/#comment-49183</guid>
		<description>[...] profitable law firm, Wachtell, Lipton, Rosen &amp; Katz which drafted this agreement, also makes mistakes. It&#8217;s also not too hard to imagine how difficult would it be for those M&amp;A practitioners [...]</description>
		<content:encoded><![CDATA[<p>[...] profitable law firm, Wachtell, Lipton, Rosen &amp; Katz which drafted this agreement, also makes mistakes. It&#8217;s also not too hard to imagine how difficult would it be for those M&amp;A practitioners [...]</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: S.</title>
		<link>http://www.adamsdrafting.com/2008/03/24/drafting-errors-bear-stearns/comment-page-1/#comment-48205</link>
		<dc:creator>S.</dc:creator>
		<pubDate>Wed, 26 Mar 2008 17:45:31 +0000</pubDate>
		<guid isPermaLink="false">http://www.adamsdrafting.com/2008/03/24/drafting-errors-bear-stearns/#comment-48205</guid>
		<description>Irony: an article about drafting errors that contains a drafting error. 

Am I the only one who sees a problem with the below sentence?

&quot;That provision could have [sic] could allow Bear’s shareholders to seek a higher bid while still forcing JPMorgan to honor its guarantee, these people said.&quot;  

Shouldn’t it say, “could have allowed”?</description>
		<content:encoded><![CDATA[<p>Irony: an article about drafting errors that contains a drafting error. </p>
<p>Am I the only one who sees a problem with the below sentence?</p>
<p>&#8220;That provision could have [sic] could allow Bear’s shareholders to seek a higher bid while still forcing JPMorgan to honor its guarantee, these people said.&#8221;  </p>
<p>Shouldn’t it say, “could have allowed”?</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Sam Maryland</title>
		<link>http://www.adamsdrafting.com/2008/03/24/drafting-errors-bear-stearns/comment-page-1/#comment-48059</link>
		<dc:creator>Sam Maryland</dc:creator>
		<pubDate>Mon, 24 Mar 2008 21:14:30 +0000</pubDate>
		<guid isPermaLink="false">http://www.adamsdrafting.com/2008/03/24/drafting-errors-bear-stearns/#comment-48059</guid>
		<description>The funny thing is on the conference call Sunday night JPM mgmt were repeatedly questioned about the &quot;guarantee&quot; of trades and it was perfectly clear that they:

(a) knew they were guaranteeing the trades.

(b) knew that it was possible they&#039;d never get the vote and the deal would break in a year.

This is  not a matter of anything &quot;inadvertent&quot;, this is a matter of JPM changing their mind and going back on what they agreed in writing to do.

What a joke.

SM</description>
		<content:encoded><![CDATA[<p>The funny thing is on the conference call Sunday night JPM mgmt were repeatedly questioned about the &#8220;guarantee&#8221; of trades and it was perfectly clear that they:</p>
<p>(a) knew they were guaranteeing the trades.</p>
<p>(b) knew that it was possible they&#8217;d never get the vote and the deal would break in a year.</p>
<p>This is  not a matter of anything &#8220;inadvertent&#8221;, this is a matter of JPM changing their mind and going back on what they agreed in writing to do.</p>
<p>What a joke.</p>
<p>SM</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Ken Adams</title>
		<link>http://www.adamsdrafting.com/2008/03/24/drafting-errors-bear-stearns/comment-page-1/#comment-48039</link>
		<dc:creator>Ken Adams</dc:creator>
		<pubDate>Mon, 24 Mar 2008 16:45:39 +0000</pubDate>
		<guid isPermaLink="false">http://www.adamsdrafting.com/2008/03/24/drafting-errors-bear-stearns/#comment-48039</guid>
		<description>China Law Blog: I&#039;m acutely aware of the pressures that M&amp;A practitioners are under. That&#039;s all the more reason to make sure your contracts are free of the clutter and dysfunction on display in the Bear Stearns merger agreement. That agreement is a chore to read, so I can only image what it was like to work with.

Do I know that murky contract language contributed to the apparent &quot;mistakes&quot;? No, but it may well have. If you want to reduce the odds of a mistake, make your contracts clearer.

And when it comes to the quality of contract language, I don&#039;t see any need to pussyfoot around. If the contract language of the Bear Stearns merger agreement is suboptimal, it&#039;s not because of any time pressures. Instead, it&#039;s because the language of the contract models used to put it together was also suboptimal.

Ken</description>
		<content:encoded><![CDATA[<p>China Law Blog: I&#8217;m acutely aware of the pressures that M&#038;A practitioners are under. That&#8217;s all the more reason to make sure your contracts are free of the clutter and dysfunction on display in the Bear Stearns merger agreement. That agreement is a chore to read, so I can only image what it was like to work with.</p>
<p>Do I know that murky contract language contributed to the apparent &#8220;mistakes&#8221;? No, but it may well have. If you want to reduce the odds of a mistake, make your contracts clearer.</p>
<p>And when it comes to the quality of contract language, I don&#8217;t see any need to pussyfoot around. If the contract language of the Bear Stearns merger agreement is suboptimal, it&#8217;s not because of any time pressures. Instead, it&#8217;s because the language of the contract models used to put it together was also suboptimal.</p>
<p>Ken</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Set in Style &#8212; Blog Archive &#187; The Risks of Sounding All-Too-Dignified</title>
		<link>http://www.adamsdrafting.com/2008/03/24/drafting-errors-bear-stearns/comment-page-1/#comment-48037</link>
		<dc:creator>Set in Style &#8212; Blog Archive &#187; The Risks of Sounding All-Too-Dignified</dc:creator>
		<pubDate>Mon, 24 Mar 2008 16:27:27 +0000</pubDate>
		<guid isPermaLink="false">http://www.adamsdrafting.com/2008/03/24/drafting-errors-bear-stearns/#comment-48037</guid>
		<description>[...] to Kenneth Adams of Adams Drafting, the error isn&#8217;t a big surprise:  . . . dysfunctional prose in M&amp;A contracts greatly increases the likelihood of a mistake [...]</description>
		<content:encoded><![CDATA[<p>[...] to Kenneth Adams of Adams Drafting, the error isn&#8217;t a big surprise:  . . . dysfunctional prose in M&amp;A contracts greatly increases the likelihood of a mistake [...]</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: China Law Blog</title>
		<link>http://www.adamsdrafting.com/2008/03/24/drafting-errors-bear-stearns/comment-page-1/#comment-48036</link>
		<dc:creator>China Law Blog</dc:creator>
		<pubDate>Mon, 24 Mar 2008 16:21:15 +0000</pubDate>
		<guid isPermaLink="false">http://www.adamsdrafting.com/2008/03/24/drafting-errors-bear-stearns/#comment-48036</guid>
		<description>Whoa, whoa, whoa.  Let he who can write a great M&amp;A contract over a weekend throw the first stone.</description>
		<content:encoded><![CDATA[<p>Whoa, whoa, whoa.  Let he who can write a great M&amp;A contract over a weekend throw the first stone.</p>
]]></content:encoded>
	</item>
</channel>
</rss>
