Skip to content

Commit 79f62df

Browse files
committed
Fix typos
1 parent 4ef059b commit 79f62df

5 files changed

+6
-6
lines changed

Rakefile

+2-2
Original file line numberDiff line numberDiff line change
@@ -73,7 +73,7 @@ end # task :post
7373

7474
# Usage: rake page name="about.html"
7575
# You can also specify a sub-directory path.
76-
# If you don't specify a file extention we create an index.html at the path specified
76+
# If you don't specify a file extension we create an index.html at the path specified
7777
desc "Create a new page."
7878
task :page do
7979
name = ENV["name"] || "new-page.md"
@@ -101,7 +101,7 @@ task :preview do
101101
system "jekyll --auto --server"
102102
end # task :preview
103103

104-
# Public: Alias - Maintains backwards compatability for theme switching.
104+
# Public: Alias - Maintains backwards compatibility for theme switching.
105105
task :switch_theme => "theme:switch"
106106

107107
namespace :theme do

_posts/news/2014-11-19-announcing-scalajs-0.5.6.md

+1-1
Original file line numberDiff line numberDiff line change
@@ -28,7 +28,7 @@ For changes introduced in 0.5.0, how to upgrade, getting started etc. have a loo
2828

2929
In Scala.js 0.6.x, putting `@JSExport` on a class or an object will export it to its fully qualified name, rather than its simple name. To ease the transition to 0.6.x, Scala.js 0.5.6 will warn if an `@JSExport` annotation without explicit name is put on a top level object or class. Otherwise, such code would silently break when migrating to 0.6.x.
3030

31-
To silence the warning, simply specify the desired name explicilty.
31+
To silence the warning, simply specify the desired name explicitly.
3232

3333
#### @JSExportDescendentClasses
3434

_posts/news/2021-01-12-announcing-scalajs-1.4.0.md

+1-1
Original file line numberDiff line numberDiff line change
@@ -47,7 +47,7 @@ As a reminder, libraries compiled with 0.6.x cannot be used with Scala.js 1.x; t
4747
### `java.lang.Class.isAssignableFrom`
4848

4949
[`java.lang.Class.isAssignableFrom` had some serious issues](https://github.com/scala-js/scala-js/issues/4328), which we fixed in Scala.js 1.4.0.
50-
It now completly follows its specification on the JVM.
50+
It now completely follows its specification on the JVM.
5151
However, it is possible that some code was relying on the broken behavior, which was, in some cases, closer to how `isInstance` and `isInstanceOf` works on Scala.js.
5252

5353
In particular, the following idiom, which we have seen before, is now broken more often than before:

_posts/news/2021-02-12-announcing-scalajs-1.5.0.md

+1-1
Original file line numberDiff line numberDiff line change
@@ -88,7 +88,7 @@ Since they are SAM types, they can be created with anonymous functions, for exam
8888
val jsFun: js.Function1[Int, String] = arg => arg.toString()
8989
{% endhighlight %}
9090

91-
The built-in JS function types can accomodate any function with a fixed number of parameters, up to 22.
91+
The built-in JS function types can accommodate any function with a fixed number of parameters, up to 22.
9292
However, they are not enough for more specialized use cases:
9393

9494
* Function values with variadic arguments (varargs)

doc/planning.md

+1-1
Original file line numberDiff line numberDiff line change
@@ -20,7 +20,7 @@ title: Planning
2020
- front page icons for Correctness, Speed and Interoperability
2121
- Documentation landing page, more content
2222

23-
## Doc content/struture plan
23+
## Doc content/structure plan
2424

2525
- Quick start
2626

0 commit comments

Comments
 (0)