if suppose the title of the particular concern is not 
spelled corectly,it would give a negative impact.eg ICICC 
is spelled as a tittle for the project of the concern 
ICICI.then it is a high severity,low priority defect.

High severity :
Eg:Calculation bugs

Low priority:    
Returning float with single decimal point with rounding the
value  instead of two decimal points can be treated as low
severity.

Eg:Expected :77.77
   Actual   :77.8

I have modules like I)Accounts II)Reports
Requirement:
The Account details which  were entered in the Accounts 
module should be reflected in the reports module.
High severity:the accounts information which were entered 
in the accounts module is showing right values in the 
accounts module but those values are not reflected in the 
Reports module.its a high severity and high priority bug 
but in some situations that Reports module is not fully 
implemented and that was in the development stage than it 
will be considered as high severity and low priority bug.

Crash of Application after 99 times clicking on OK button
Severity :- High as it is a Crash
Priority :- Low as rarely used scenario

In any application the application will be crashed the 
multiple use of any fucnality.for ex save button use 200 
times. The application will be crashed. So high severity. 
but low priority. Because there is need to debug the right 
now u can debug it after some days

it can be explianed with a simple example: say u are 
developing a project on jet air ways and each page have an 
air jet pix, but if one page is displayed with a different 
image (ex:say with a scooter) it doesnot effect the 
application much, but it would be really painfull for 
clientot user to see that pix in between the site..., so 
here it is high severity (means we have to change it imm. 
even though it doesnt effect the system or appication)but 
its with low priority.

High Severity -  Suddenly ATM Machin get crashed

Low Periority - Speeling mistake on perticular web page.

Thankx