> For the complete documentation index, see [llms.txt](https://www.indiainvestments.wiki/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://www.indiainvestments.wiki/contributors/style-guides/stocks-style-guide.md). # Stocks Style Guide This article is meant to serve as a style guide on how to write content in the [Stocks](/stocks/can-you-beat-the-market.md) section. This isn’t a strict requirement but a general recommendation or advice about how to approach writing content which meets the level of quality we’re looking for in the Stocks section. This is in addition to our general style guide {% content-ref url="/pages/-MUhXHTdifsuHV9ZkCaI" %} [General Style Guide](/contributors/style-guides/general-style-guide.md) {% endcontent-ref %} ### Use Beginner Friendly Writing Style Unless something has already been covered in one of the sections written before, please don’t assume that the reader would know about it. This doesn’t mean that content should be dumbed down, but it should be easy to approach such that understanding it doesn’t feel uncomfortable. This might be a bit hard to grasp but don’t write as if you’re a robot writing dry commentary or producing *TL;DR* styled content. Write as if you’re thinking out loud in your own mind although avoid using first person references like *I*, *me*, *you* etc. Using *we*, *oneself*, *one can assume…* is preferable. ### Use Examples Use actual examples that readers can relate to. Talking about something and actually showing how it happens in real life are vastly different things. If talking about valuation, use an example that shows how to arrive at it. If talking about a financial ratio, use images from an annual report and show the reader how to calculate that ratio. In other words, show the reader how & from where input values needed to calculate a ratio are derived from. For example, while explaining how to calculate Working Capital of a company, insert a screenshot showing Current Assets and Current Liabilities of a company in its balance sheet. ### Dive Deep Into Details When Necessary If, and when, necessary, feel free to dive into details while keeping efficiency in mind. In such cases, try to understand the entire concept yourself, sketch out a summary or a bird's-eye view of the concept, and then write about it. If a wall of text has to be written, try to make it engaging and somewhat fun to read by adding relevant images, examples, and other interactive elements. ### Use Consolidated Financial Statements Unless there's a good reason to focus on standalone financial statements, use consolidated financial statements when presenting examples. ### When in doubt, ask If you’re writing content for a chapter and feel stuck in any part of the process, do let us know. We’d love to guide you on what needs to be covered, and how. We’ve a draft of talking points for each chapter of the series, and a rough idea on how they need to be explained. Feel free to DM the core contribution team, or drop a message in #kb-due-diligence for any help regarding coverage, structuring, phrasing or any other issues you face while contributing. --- # Agent Instructions This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com. ## Querying This Documentation If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question. Perform an HTTP GET request on the current page URL with the `ask` query parameter: ``` GET https://www.indiainvestments.wiki/contributors/style-guides/stocks-style-guide.md?ask= ``` The question should be specific, self-contained, and written in natural language. The response will contain a direct answer to the question and relevant excerpts and sources from the documentation. Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.