In one sentence, describe what the following article is about: In order to understand the scoring system, you will need to know the value of the cards. The values don’t change throughout the game. Playing the cards in a “meld” during your turn nets you points, but holding onto the cards at the end of the round costs you points.  Jokers are worth 50 points. Aces and deuces are worth 20 points. Any card from an 8 to a King is worth 10 points. Cards ranked from 4 to 7 are worth only 5 points. Black 3s are also worth 5 points if you are able to use them. Red 3s are different from the other cards and are kept separate on the table. Each red 3 is worth 100 points. As soon as you get one, lay it face up in front of you. Collect as many of the red 3s as you can for bigger bonuses.  If you get all of the red 3s during a round, they are worth 200 points each. There are 4 of them in total, adding up to 800 points. It is rare, but it will put you way ahead of the competition. Failing to play a red 3 by the end of a round nets you a 500 point penalty, so be careful! That gives your partner a chance to pick up the discard pile on his turn. Black 3s also have some additional scoring quirks for you to be aware of. Black 3s can only be melded for points when they are the last cards in your hand. For that reason, they tend to be more useful for throwing off your opponents than scoring points. Think of these cards as replacements for ones you’re missing in your hand. When you score points by matching at least 3 cards of the same rank, use a wildcard to replace another missing card. These cards also allow you to freeze the discard pile to prevent your opponent from taking it. If you do this, turn the card sideways on the discard pile to indicate it is frozen.  For example, if you have 2 jacks, you could complete a meld by playing a 2 with it. Place the set of cards face up in front of you. You need to have 2 natural, matching cards to begin a meld. You can't start a meld with 2 wildcards, but you can use up to 3 of them to finish a meld. Normally, you freeze the discard pile with a wildcard when you are desperate. When the pile is frozen this way, nobody can take the discard pile until someone uses the top card to make a natural meld. There are a few different types of melds to keep in mind as you play. Each meld must have at least 2 natural cards in order to be valid. You can add wildcards to the meld in order to score more points and make game-changing moves like completing a 7-card canasta.  A meld of 7 cards is a canasta. A natural canasta, or one with no wildcards, is worth 500 bonus points. A dirty or mixed canasta, which has at least 1 wildcard, is worth 300 bonus points. The goal of the game is to make as many canastas as you can before the game ends. In fact, most rules force you to make at least 1 before you are able to stop playing a round.
Summary: Memorize the point value of all the scoring cards in the game. Use red 3s as a bonus card to score additional points. Play black 3s to block the next player in turn from taking the discard pile. Use jokers and 2s as wildcards to score or freeze. Make different melds to score points during the game.

In one sentence, describe what the following article is about: Although the functional reason for documenting software is to help users understand how to use the application, there are other reasons as well, such as assisting in marketing the software, enhancing the company image, and most notably, reducing technical support costs. In some cases, documentation is necessary to comply with certain regulations or other legal requirements. In no case, however, should software documentation substitute for poor interface design. If an application screen requires reams of documentation to explain it, better to change the screen design to something more intuitive. In most cases, software users have little knowledge of computers outside of the tasks the applications they use enable them to do. There are several ways to determine how to address their needs with your documentation.  Look at the job titles your prospective users hold. A system administrator is likely expert with a number of software applications, while a data entry clerk is more likely to know only the application he or she currently uses to enter data. Look at the users themselves. Although job titles generally indicate what people do, there can be considerable variation in how certain titles are used within a given organization. By interviewing prospective users, you can get a feel for whether your impressions of what their job title indicates are accurate or not. Look at existing documentation. Documentation for previous versions of software, as well as functional specifications, provide some indication as to what the user will need to know to use the program. Keep in mind, however, that end users are not as interested in how the program works as they are in what it can do for them. Identify the tasks needed to do the job, and what tasks need to be done before those tasks can be done. Software documentation can be structured in 1 of 2 formats, the reference manual and the user guide. Sometimes, a combination of formats is the best approach.  A reference manual format is devoted to explaining the individual features of a software application (button, tab, field, and dialog box) and how they work. Many help files are written in this format, particularly context-sensitive help that displays a relevant topic whenever a user clicks the Help button on a particular screen.  A user guide format explains how to use the software to perform a particular task. User guides are often formatted as printed guides or PDFs, although some help files include topics on how to perform particular tasks. (These help topics are usually not context-sensitive, although they may be hyperlinked to from topics that are.) User guides often take the form of tutorials, with a summary of the tasks to be performed in the introduction and instructions given in numbered steps. Software documentation for end users can take 1 or several of many forms: printed manuals, PDF documents, help files, or online help. Each form is designed to show the user how to use each of the program's functions, whether in the form of a walkthrough or a tutorial; in the case of help files and online help, this may include demonstration videos as well as text and still graphics. Help files and online help should be indexed and keyword-searchable to allow users to quickly find the information they're looking for. Although help file authoring tools can generate indexes automatically, it is often better to create the index manually, using terms users are likely to search for. Printed or PDF user manuals can be written with a word-processing program like Word or a sophisticated text editor like FrameMaker, depending on their length and complexity. Help files can be written with a help authoring tool like RoboHelp, Help and Manual, Doc-To-Help, Flare, HelpLogix, or HelpServer.
Summary:
Determine the business reasons for your documentation. Understand the audience you're writing the documentation for. Determine the appropriate format(s) for the documentation. Decide what form(s) the documentation should take. Choose the appropriate documentation tool.