# Project associated texts Localizing a project is not just translating the website or app strings. There is a lot of other text artifacts that should be localized: * Short and long descriptions for app stores * Product "what's new" and change logs * Various "about" texts you use over and over * Social greetings * E-mail introductions * and more To keep all these texts altogether, translate and proofread them, use the "Associated texts" section of your project. ## Adding an associated text You can add an associated text at any time. All you need is to specify a text. New text immediately gets translated automatically and goes to the "Translations" section for proofreading. You may use the translation immediately, or wait for your team to fix the particular translations. ## Editing an associated text You may want to edit or update an associated text. When this happens, all team proofreaders receive a "re-check" notification (like if you click "request re-check" for a translation). BabelShark keeps the history of your associated text editions so you may check or pick an older version at any time. ## Recommendations


Texts for app stores	Create a single associated text and edit it whenever you need to update it.	Proofreaders will get a notification that text is updated.
"What's new"	Create a new associated text for each of your updates. Older updates may be deleted or stored.	Proofreaders will get a notification about a new text to check.
Changelogs	Create a new small associated text for each record in your changelog.	Proofreaders will read each new record separately. This saves the time and wallet.

### Team availability * The project owner and managers: * able to read, add and update associated * able to edit associated text translations * Proofreaders: * able to view and edit associated text translations for their languages.