Cleaned up readme slightly

Removed old entry in ISSUES that was fixed earlier

Author: msoucy

ISSUES

@@ -1,11 +1,7 @@
-ACS_vars:
-	They do not currently match the C version, but I think that this is as close as we can get.
-	See examples/acs_vars.d to see how they are to be used. If this changes, I'll simply deprecate the old way.
-
 Mouse Events:
-	This one is a little tricky since most of this is system specific... 
+	This one is a little tricky since most of this is system specific...
 	Some of the functions haven't been implemented yet...
 
 Other Files:
-	There are several other files listed in the include/ncurses folder.  things like termcap.h and a few that 
-	look to be higher-level wrappers..  How much should be included?
+	There are several other files listed in the include/ncurses folder.  things like termcap.h and a few that
+	look to be higher-level wrappers..  How much should be included?

README

@@ -4,12 +4,6 @@ There will be bugs.  This is simply too large of a library for me to test every
 If you have any trouble, or think that something should be fixed, create a bug report and I'll get right on it.
 
 WARNINGS:
-	ACS vars currently break from the norm, I'm looking into it, but I'm not sure if It can
-	be done exactly the same that C does it.
-	////instead of writing "addch(ACS_ULCORNER);", Instead write "addch(acs_map[ACS.ULCORNER]);". fixed
-	Instead of writing "addch(ACS_ULCORNER);", Instead write "addch(ACS_ULCORNER());"
-	I think that this is as close as we are going to get without digging through the source to extract what acs_map[] really is.
-
 	This should work for most of your needs, however there are still one or two more things that need to be done.
 	I plan on having those completed in the next few days.
 	I'm actually not entirely sure what still needs to be done.  Someone told me that this was a macro library.
@@ -19,5 +13,5 @@ WARNINGS:
 	I'll continue to get the other headers translated, things like termcap.h will be added soon.
 	I simply need more eyes on this to bug check and ensure that things are working properly.
 
-	If you are familiar with the FREE acronym(Functional, Reliable, Elegant, Efficient) I would say we are an F.
-	I doubt we can get any farther than FR, but let's go for it!
+If you are familiar with the FREE acronym(Functional, Reliable, Elegant, Efficient) I would say we are an F.
+I doubt we can get any farther than FR, but let's go for it!