You operate a community website where registered users may post rating and reviews of area restaurants. Each registered user has a unique user name, along with a first name, last name, address information, e-mail address, and phone number; however, your public website displays only the screen name. For each restaurant, you want to store a name, address information, phone number, website URL, category ("kebabhouse", "Chinese", etc.). Each review consists of a single registered user's opinion of a single restaurant, and consists of a food quality rating on a scale of 1 to 5, dinner cost paid per person, and comments (up to 255 characters text, such as "the crab cakes are excellent"). Each registered user may review many restaurants, and also allowed to have multiple reviews for the restaurants on different visits.

Now suppose that we find out that only 5% of the users write comments about the restaurant while reviewing. In most reviews users rate the restaurant but they dont write comments. Draw a new entity-relationship diagram and rewrite the database design outline.