From ed7a980a8556e7ea0ab5840d130f9accc83bf7ff Mon Sep 17 00:00:00 2001
From: "Jiten (OpenERP)" <jra@tinyerp.com>
Date: Fri, 14 Sep 2012 14:58:32 +0530
Subject: [PATCH] [IMP] minor change to add <p> on text context.

bzr revid: jra@tinyerp.com-20120914092832-sbu30zjrkx5y2j18
---
 addons/procurement/procurement_view.xml | 2 ++
 1 file changed, 2 insertions(+)

diff --git a/addons/procurement/procurement_view.xml b/addons/procurement/procurement_view.xml
index ba0d4506709..bf73b383216 100644
--- a/addons/procurement/procurement_view.xml
+++ b/addons/procurement/procurement_view.xml
@@ -167,7 +167,9 @@
             <field name="context">{'search_default_perm_exceptions':1}</field>
             <field name="search_view_id" ref="view_procurement_filter"/>
             <field name="help" type="html">
+                <p>
                 Procurement Orders represent the need for a certain quantity of products, at a given time, in a given location. Sales Orders are one typical source of Procurement Orders (but these are distinct documents). Depending on the procurement parameters and the product configuration, the procurement engine will attempt to satisfy the need by reserving products from stock, ordering products from a supplier, or passing a manufacturing order, etc. A Procurement Exception occurs when the system cannot find a way to fulfill a procurement. Some exceptions will resolve themselves automatically, but others require manual intervention (those are identified by a specific error message).
+                </p>
             </field>
         </record>