True/False In describing technical communication, the author argues that it is both a process of making and a process of sharing documents. Technical communications includes all of the following: textbooks, phone books. Web sites, journal articles and owner's manuals. Technical documents are rarely consistent with an organization's goals. Technical documents typically don't reflect an organization's culture. The author argues that ethics within an organization may be derived from either or both "gut feelings' or religious or "golden rule" standard(s). According to the author, academic and workplace research should meet the same standards of scrutiny. Ethical and legal obligations are often closely related. Copyright laws ensure that the public recognizes the name or logo of a product. Trademark violations are not serious legal issues and there is no civil liability for such an act. Never try to analyze your target audience by having conversations with them - as it may prejudice the outcome. A good way to start in planning for technical documentation is to review similar existing documentation in your organization's archives. Templates should be avoided in writing technical documentation because of copyright laws. It is not a good idea to seek the help of co-workers when editing or proofreading a draft document. According to the author, when conducting a meeting you should avoid interrupting a speaker unless you need to clarify what they are saying. The question "why is your audience reading your document" is not important for technical writers as their audience must read documentation provided. According to the author, a linguistic cultural variable is an example of a "beneath the surface" variable. One conventional "pattern of arrangement" is spatial. A problem-method-solution pattern system of organizing is rarely used to carry out aa project. Technical communication often involves cause-and-effect discussions. It is always appropriate to apply "conventional patterns of arrangement" to organizing technical writing. An executive summary is an example of a "general to specific" organizing pattern