Q: Choose the color, size, and length of the lights you want to wrap around your Christmas tree. Determine the ideal length you’ll need by taking a couple measurements of the tree’s circumference with flexible measuring tape.  Try opting for a longer string than you think you need, or multiple strings, as the tree will look best with lights weaved into the inside of the tree, not just the outside branches. A good rule is to have a string of 100 lights for every vertical foot of the tree.  You can mix and match colors and styles of lights on the same tree. Try smaller traditional incandescent lights in multi-color along with a string of larger white globe lights, for example, to add variety to your tree. Hang a garland of beads, ribbon, or foil on your tree by loosely draping it over the branches from top to bottom.  Try making your own traditional garlands by stringing popcorn kernels or cranberries together. A good rule is to hang a thin garland of berries, beads, or popcorn by draping it across the branches, while a thicker ribbon or foil garland should be wrapped loosely around the tree. You can also add loose tinsel to hang on the garlands, strings of lights, or the branches themselves. Or, find a string of tinsel to hang like a garland for less fallen mess. Place ornaments on the tree by spacing them evenly throughout all sides of the tree on top and bottom.  Try placing your favorite ornaments, whether they’re sentimental or just visually pleasing, up front and in the middle of the tree where you will see them most often. Then space all of your largest ornaments around the tree before filling in with smaller ones. Make sure to hang ornaments, especially fragile ones, securely on the tree by pinching the wire hanger (either provided or one you’ve made with a paper clip) securely around the branch you’re hanging on. You can also add other touches to the tree at this point, like a star or angel tree topper, poinsettia flowers, or other adornments like icicles and snowflakes.
A: String up lights. Wrap a garland around the tree. Hang your ornaments.

Q: It can be tempting to use a word processor (e.g., Microsoft Word) or a similar program to create a rich-text document, but pseudocode needs as little formatting as possible to keep it simple. Dedicating a line or two to explaining the purpose of your code will help set up the rest of the document, and it will also save you the task of explaining the program's function to each person to whom you show the pseudocode. Each statement in your pseudocode should express just one action for the computer. In most cases, if the task list is properly drawn, then each task will correspond to one line of pseudocode. Consider writing out your task list, then translating that list into pseudocode, then gradually developing that pseudocode into actual, computer-readable code. Using white spaces between "blocks" of text will help keep different components of your pseudocode isolated, and indenting different pieces of each block will indicate that those pieces of pseudocode go under a less-indented section. For example, a section of pseudocode that discusses entering a number should all be in the same "block", while the next section (e.g., the section that discusses the output) should be in a different block. Depending on your pseudocode requirements or the environment in which you're publishing the pseudocode, you may need to capitalize commands that will remain in the actual code. For example, if you use "if" and "then" commands in your pseudocode, you might want to change them to read "IF" and "THEN" (e.g., "IF input number THEN output result"). Remember, you're writing about what the project will do, not summarizing the code itself. This is especially important if you're writing pseudocode to serve as a demonstration for a customer who doesn't know coding, or as a project for a beginner programmer. While the language you use to modify your pseudocode should be simple, you still need to keep each piece of your pseudocode in the order in which it needs to be executed. Everything that is happening in the process must be described completely. Pseudocode statements are close to simple English statements. Pseudocode does not typically use variables, but instead describes what the program should do with close-to-real-world objects such as account numbers, names, or transaction amounts. Even if there is no standard for pseudocode, it will be easier for other programmers to understand your steps if you use structures from existing (sequential) programming languages. Use terms like "if", "then", "while", "else", and "loop" the same way that you would in your preferred programming language. Consider the following structures:   if CONDITION then INSTRUCTION — This means that a given instruction will only be conducted if a given condition is true. "Instruction", in this case, means a step that the program will perform, while "condition" means that the data must meet a certain set of criteria before the program takes action.   while CONDITION do INSTRUCTION — This means that the instruction should be repeated again and again until the condition is no longer true.   do INSTRUCTION while CONDITION — This is very similar to "while CONDITION do INSTRUCTION". In the first case, the condition is checked before the instruction is conducted, but in the second case the instruction will be conducted first; thus, in the second case, INSTRUCTION will be conducted at least one time.  function NAME (ARGUMENTS): INSTRUCTION — This means that every time a certain name is used in the code, it is an abbreviation for a certain instruction. "Arguments" are lists of variables that you can use to clarify the instruction. If you have large sections of pseudocode that define other pieces of pseudocode within the same block, you may want to use brackets or other identifiers to keep everything contained.  Brackets—both standard (e.g., [code]) and curved (e.g., {code})—can help contain long segments of pseudocode. When coding, you can add comments by typing "//" on the left side of the comment (e.g., //This is a temporary step.). You can use this same method when writing pseudocode to leave notes that don't fit into the coding text. You should be able to answer the following questions by the end of the document:  Would this pseudocode be understood by someone who isn't familiar with the process? Is the pseudocode written in such a way that it will be easy to translated it into a computing language? Does the pseudocode describe the complete process without leaving anything out? Is every object name used in the pseudocode clearly understood by the target audience? If you find that a section of pseudocode needs elaboration or it doesn't explicitly outline a step that someone else might forget, go back and add the necessary information.
A:
Use a plain-text editor. Start by writing down the purpose of the process. Write only one statement per line. Use white space and indentation effectively. Capitalize key commands if necessary. Write using simple terminology. Keep your pseudocode in the proper order. Leave nothing to the imagination. Use standard programming structures. Organize your pseudocode sections. Double-check your pseudocode for readability and clarity.