Skip to content

Commit 7e1e6ac

Browse files
christinerosepanglesd
authored andcommitted
minor formatting
1 parent aac129e commit 7e1e6ac

File tree

1 file changed

+15
-15
lines changed

1 file changed

+15
-15
lines changed

README.md

Lines changed: 15 additions & 15 deletions
Original file line numberDiff line numberDiff line change
@@ -17,18 +17,18 @@
1717
</a>
1818
</p>
1919

20-
**odoc** is a powerful and flexible documentation generator for OCaml. It reads *doc comments*, demarcated by `(** ... *)`, and transforms them into a variety of output formats, including HTML, LaTeX, and man pages.
20+
**`odoc`** is a powerful and flexible documentation generator for OCaml. It reads *doc comments*, demarcated by `(** ... *)`, and transforms them into a variety of output formats, including HTML, LaTeX, and man pages.
2121

22-
- **Output Formats:** Odoc generates HTML for web browsing, LaTeX for PDF generation, and man pages for use on Unix-like systems.
23-
- **Cross-References:** odoc uses the `ocamldoc` markup, which allows to create links for functions, types, modules, and documentation pages.
22+
- **Output Formats:** `odoc` generates HTML for web browsing, LaTeX for PDF generation, and man pages for use on Unix-like systems.
23+
- **Cross-References:** `odoc` uses the `ocamldoc` markup, which allows users to create links for functions, types, modules, and documentation pages.
2424
- **Link to Source Code:** Documentation generated includes links to the source code of functions, providing an easy way to navigate from the docs to the actual implementation.
25-
- **Code Highlighting:** odoc automatically highlights syntax in code snippets for different languages.
25+
- **Code Highlighting:** `odoc` automatically highlights syntax in code snippets for different languages.
2626

27-
odoc is part of the [OCaml Platform](https://ocaml.org/docs/platform), the recommended set of tools for OCaml.
27+
`odoc` is part of the [OCaml Platform](https://ocaml.org/docs/platform), the recommended set of tools for OCaml.
2828

2929
## Getting Started
3030

31-
To begin using odoc, first install it using opam with the following command:
31+
To begin using `odoc`, first install it using opam with the following command:
3232

3333
```
3434
$ opam install odoc
@@ -46,27 +46,27 @@ Upon completion, you'll find your freshly minted docs in `_build/default/_doc/_h
4646
$ open _build/default/_doc/_html/index.html
4747
```
4848

49-
For more in-depth information and usage instructions, see the [odoc website](https://ocaml.github.io/odoc).
49+
For more in-depth information and usage instructions, see the [`odoc` website](https://ocaml.github.io/odoc).
5050

5151
## Documentation
5252

53-
The full documentation for odoc, including comprehensive user and API guides, can be found on our [website](https://ocaml.github.io/odoc/).
53+
The full documentation for `odoc`, including comprehensive user and API guides, can be found on our [website](https://ocaml.github.io/odoc/).
5454

5555
## Contributing
5656

5757
### [Contributing Guide](CONTRIBUTING.md)
5858

59-
We wholeheartedly welcome contributors! To start, please read our [Contributing Guide](CONTRIBUTING.md) to familiarize yourself with our development process, including how to propose and how to start hacking on odoc.
59+
We wholeheartedly welcome contributors! To start, please read our [Contributing Guide](CONTRIBUTING.md) to familiarise yourself with our development process, including how to propose and how to start hacking on `odoc`.
6060

6161
### [Code of Conduct][coc]
6262

63-
In order to foster a welcoming and respectful community, odoc has adopted the [OCaml Code of Conduct](coc).
63+
In order to foster a welcoming and respectful community, `odoc` has adopted the [OCaml Code of Conduct](coc).
6464

6565
[coc]: https://ocaml.org/policies/code-of-conduct
6666

6767
### [Roadmap](ROADMAP.md)
6868

69-
Interested in the future of odoc? Take a look at our [Roadmap](ROADMAP.md) to understand our vision and planned advancements for odoc.
69+
Interested in the future of `odoc`? Take a look at our [Roadmap](ROADMAP.md) to understand our vision and planned advancements for `odoc`.
7070

7171
### [Discussions][discussions]
7272

@@ -76,12 +76,12 @@ For conversations on ongoing development, be sure to visit the [odoc][discussion
7676

7777
## License
7878

79-
odoc is distributed under the terms of the ISC License. See the [LICENSE](LICENSE) file for complete details.
79+
`odoc` is distributed under the terms of the ISC License. See the [LICENSE](LICENSE) file for complete details.
8080

8181
## Acknowledgments
8282

83-
odoc owes its existence to the efforts of [Thomas Refis](https://github.com/trefis), [Leo White](https://github.com/lpw25), and [David Sheets](https://github.com/dsheets). The project was initiated in 2014 and 2015.
83+
`odoc` owes its existence to the efforts of [Thomas Refis](https://github.com/trefis), [Leo White](https://github.com/lpw25), and [David Sheets](https://github.com/dsheets). The project was initiated in 2014 and 2015.
8484

85-
We'd also like to extend our appreciation to [Anton Bachin](https://github.com/aantron) and [Daniel Bünzli](https://github.com/dbuenzli) and [Jon Ludlam](https://github.com/jonludlam) for their pivotal contributions to odoc.
85+
We'd also like to extend our appreciation to [Anton Bachin](https://github.com/aantron), [Daniel Bünzli](https://github.com/dbuenzli), and [Jon Ludlam](https://github.com/jonludlam) for their pivotal contributions to `odoc`.
8686

87-
Furthermore, we express our gratitude to [Jane Street](https://www.janestreet.com/) and [Tarides](https://tarides.com/), whose funding has been critical to support the ongoing development of odoc.
87+
Furthermore, we express our gratitude to [Jane Street](https://www.janestreet.com/) and [Tarides](https://tarides.com/), whose funding has been critical to support the ongoing development of `odoc`.

0 commit comments

Comments
 (0)