Skip to content

[Docs] Fixes typos and spacing #1318

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Merged
merged 1 commit into from
Mar 7, 2017
Merged

[Docs] Fixes typos and spacing #1318

Changes from all commits
Commits
Show all changes
1 commit
Select commit
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
14 changes: 7 additions & 7 deletions site/docsource/OCaml-call-JS.adoc
View file
Open in desktop
Original file line number Diff line number Diff line change
@@ -1,4 +1,4 @@
## BuckleScritp annotations for Unicode and JS FFI support
## BuckleScript annotations for Unicode and JS FFI support

To make OCaml work smoothly with Javascript, we introduced several
extensions to the OCaml language. These BuckleScript extensions
Expand All @@ -12,7 +12,7 @@ improve the generated code.
In this section, we assume the source is encoded using UTF8
========

In OCaml, string is an immutable byte sequence(like GoLang), so if user type some Unicode
In OCaml, string is an immutable byte sequence (like GoLang), so if user type some Unicode

[source,ocaml]
--------------
Expand Down Expand Up @@ -1231,7 +1231,7 @@ var v2 = {
};
-----------

Compiler infer the type of `v2` as below:
Compiler infers the type of `v2` as below:
[source,ocaml]
--------------
val v2 : object
Expand Down Expand Up @@ -1301,7 +1301,7 @@ f.open
f.MAX_LENGTH
-----------

Second, it is common to have several types for a single method, to model
Second, it is common to have several types for a single method, to model
this ad-hoc polymorphism, we introduced a small convention when translating
object labels, this is _occasionally_ useful as below

Expand Down Expand Up @@ -1341,7 +1341,7 @@ In general, the FFI code is error prone, and potentially will leak in

So we introduced auto coercion for return values for two benefits:

1. More safety for FFI code without performance cost(explained later)
1. More safety for FFI code without performance cost (explained later)

2. More idiomatic OCaml code for users to consume the FFI.

Expand All @@ -1360,7 +1360,7 @@ let test dom =
| None -> 1
| Some ui -> Js.log ui ; 2
-------------
<1> `null_to_opt` attriute will automatically convert null to `option`
<1> `null_to_opt` attribute will automatically convert null to `option`

.Output
[source,js]
Expand Down Expand Up @@ -1516,7 +1516,7 @@ var f = /b/g
------------


NOTE: `Js.Re.t` is an abstract type, we are working on providing
NOTE: `Js.Re.t` is an abstract type, we are working on providing
bindings for it.


Expand Down