balsoft/ligo
1
0
Fork 0
Code Issues Pull Requests Releases Wiki Activity

Doc: fixed typo s/developper/developer/

Browse Source
This commit is contained in:
Jonathan 2018-04-17 09:44:00 +00:00 committed by Grégoire Henry
parent 40e63739ac
commit 92ee761451
3 changed files with 4 additions and 4 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

4
docs/index.rst
View File

@ -4,8 +4,8 @@
contain the root `toctree` directive. contain the root `toctree` directive.
Welcome to the Tezos Developper Documentation! Welcome to the Tezos Developer Documentation!
============================================== =============================================
Tezos is a distributed consensus platform with meta-consensus Tezos is a distributed consensus platform with meta-consensus
capability. Tezos not only comes to consensus about the state of its ledger, capability. Tezos not only comes to consensus about the state of its ledger,

2
docs/introduction/alphanet_changes.rst
View File

@ -73,7 +73,7 @@ Reset 2017-11-20
- Refactor the economic protocol amendment code. Protocols are - Refactor the economic protocol amendment code. Protocols are
now compiled to functors, taking the type signature of their now compiled to functors, taking the type signature of their
runtime environment as parameter. This simplifies the runtime environment as parameter. This simplifies the
dependencies, and will allow third party developpers to dependencies, and will allow third party developers to
instanciate economic protocols in other contexts than the node. instanciate economic protocols in other contexts than the node.
- Switch from Makefiles to jbuilder, yay! - Switch from Makefiles to jbuilder, yay!

2
docs/whitedoc/the_big_picture.rst
View File

@ -8,7 +8,7 @@ readable by anyone, describes the main elements of Tezos from a
distance. It abstracts from all plumbing and both internal and system distance. It abstracts from all plumbing and both internal and system
dependencies to give a simple view of the main components, their dependencies to give a simple view of the main components, their
responsibilities and interactions. The second part is written for responsibilities and interactions. The second part is written for
developpers, and is at the level of OPAM packages. developers, and is at the level of OPAM packages.
The Big Picture The Big Picture
--------------- ---------------