Skip to content

Commit 319fc9c

Browse files
authored
Spelling (#1820)
* spelling: , and Signed-off-by: Josh Soref <2119212+jsoref@users.noreply.github.com> * spelling: , the Signed-off-by: Josh Soref <2119212+jsoref@users.noreply.github.com> * spelling: ; otherwise, Signed-off-by: Josh Soref <2119212+jsoref@users.noreply.github.com> * spelling: a Signed-off-by: Josh Soref <2119212+jsoref@users.noreply.github.com> * spelling: about Signed-off-by: Josh Soref <2119212+jsoref@users.noreply.github.com> * spelling: accelerate Signed-off-by: Josh Soref <2119212+jsoref@users.noreply.github.com> * spelling: accepted Signed-off-by: Josh Soref <2119212+jsoref@users.noreply.github.com> * spelling: access Signed-off-by: Josh Soref <2119212+jsoref@users.noreply.github.com> * spelling: across Signed-off-by: Josh Soref <2119212+jsoref@users.noreply.github.com> * spelling: additional Signed-off-by: Josh Soref <2119212+jsoref@users.noreply.github.com> * spelling: all members Signed-off-by: Josh Soref <2119212+jsoref@users.noreply.github.com> * spelling: also need to Signed-off-by: Josh Soref <2119212+jsoref@users.noreply.github.com> * spelling: an existing Signed-off-by: Josh Soref <2119212+jsoref@users.noreply.github.com> * spelling: and Signed-off-by: Josh Soref <2119212+jsoref@users.noreply.github.com> * spelling: annotation Signed-off-by: Josh Soref <2119212+jsoref@users.noreply.github.com> * spelling: attachment Signed-off-by: Josh Soref <2119212+jsoref@users.noreply.github.com> * spelling: available Signed-off-by: Josh Soref <2119212+jsoref@users.noreply.github.com> * spelling: band Signed-off-by: Josh Soref <2119212+jsoref@users.noreply.github.com> * spelling: base directory of the project to the plugin Signed-off-by: Josh Soref <2119212+jsoref@users.noreply.github.com> * spelling: benefiting Signed-off-by: Josh Soref <2119212+jsoref@users.noreply.github.com> * spelling: between Signed-off-by: Josh Soref <2119212+jsoref@users.noreply.github.com> * spelling: boundaries Signed-off-by: Josh Soref <2119212+jsoref@users.noreply.github.com> * spelling: cannot Signed-off-by: Josh Soref <2119212+jsoref@users.noreply.github.com> * spelling: committee Signed-off-by: Josh Soref <2119212+jsoref@users.noreply.github.com> * spelling: committing Signed-off-by: Josh Soref <2119212+jsoref@users.noreply.github.com> * spelling: communication Signed-off-by: Josh Soref <2119212+jsoref@users.noreply.github.com> * spelling: compatible Signed-off-by: Josh Soref <2119212+jsoref@users.noreply.github.com> * spelling: construction Signed-off-by: Josh Soref <2119212+jsoref@users.noreply.github.com> * spelling: creative Signed-off-by: Josh Soref <2119212+jsoref@users.noreply.github.com> * spelling: delimited Signed-off-by: Josh Soref <2119212+jsoref@users.noreply.github.com> * spelling: disables Signed-off-by: Josh Soref <2119212+jsoref@users.noreply.github.com> * spelling: displayed Signed-off-by: Josh Soref <2119212+jsoref@users.noreply.github.com> * spelling: ecosystem Signed-off-by: Josh Soref <2119212+jsoref@users.noreply.github.com> * spelling: efficient Signed-off-by: Josh Soref <2119212+jsoref@users.noreply.github.com> * spelling: entities Signed-off-by: Josh Soref <2119212+jsoref@users.noreply.github.com> * spelling: environment Signed-off-by: Josh Soref <2119212+jsoref@users.noreply.github.com> * spelling: ergonomic Signed-off-by: Josh Soref <2119212+jsoref@users.noreply.github.com> * spelling: example Signed-off-by: Josh Soref <2119212+jsoref@users.noreply.github.com> * spelling: fallback Signed-off-by: Josh Soref <2119212+jsoref@users.noreply.github.com> * spelling: february Signed-off-by: Josh Soref <2119212+jsoref@users.noreply.github.com> * spelling: follow ups Signed-off-by: Josh Soref <2119212+jsoref@users.noreply.github.com> * spelling: from Signed-off-by: Josh Soref <2119212+jsoref@users.noreply.github.com> * spelling: functionalities Signed-off-by: Josh Soref <2119212+jsoref@users.noreply.github.com> * spelling: further Signed-off-by: Josh Soref <2119212+jsoref@users.noreply.github.com> * spelling: genuine Signed-off-by: Josh Soref <2119212+jsoref@users.noreply.github.com> * spelling: github Signed-off-by: Josh Soref <2119212+jsoref@users.noreply.github.com> * spelling: greater Signed-off-by: Josh Soref <2119212+jsoref@users.noreply.github.com> * spelling: however Signed-off-by: Josh Soref <2119212+jsoref@users.noreply.github.com> * spelling: html pages Signed-off-by: Josh Soref <2119212+jsoref@users.noreply.github.com> * spelling: https: Signed-off-by: Josh Soref <2119212+jsoref@users.noreply.github.com> * spelling: implicitly Signed-off-by: Josh Soref <2119212+jsoref@users.noreply.github.com> * spelling: implicits Signed-off-by: Josh Soref <2119212+jsoref@users.noreply.github.com> * spelling: inaugural Signed-off-by: Josh Soref <2119212+jsoref@users.noreply.github.com> * spelling: include Signed-off-by: Josh Soref <2119212+jsoref@users.noreply.github.com> * spelling: including Signed-off-by: Josh Soref <2119212+jsoref@users.noreply.github.com> * spelling: infrastructure Signed-off-by: Josh Soref <2119212+jsoref@users.noreply.github.com> * spelling: initial Signed-off-by: Josh Soref <2119212+jsoref@users.noreply.github.com> * spelling: into an Signed-off-by: Josh Soref <2119212+jsoref@users.noreply.github.com> * spelling: into Signed-off-by: Josh Soref <2119212+jsoref@users.noreply.github.com> * spelling: it's a Signed-off-by: Josh Soref <2119212+jsoref@users.noreply.github.com> * spelling: its Signed-off-by: Josh Soref <2119212+jsoref@users.noreply.github.com> * spelling: javascript Signed-off-by: Josh Soref <2119212+jsoref@users.noreply.github.com> * spelling: jira Signed-off-by: Josh Soref <2119212+jsoref@users.noreply.github.com> * spelling: little Signed-off-by: Josh Soref <2119212+jsoref@users.noreply.github.com> * spelling: macos Signed-off-by: Josh Soref <2119212+jsoref@users.noreply.github.com> * spelling: maintaining Signed-off-by: Josh Soref <2119212+jsoref@users.noreply.github.com> * spelling: many, many, Signed-off-by: Josh Soref <2119212+jsoref@users.noreply.github.com> * spelling: mastodon Signed-off-by: Josh Soref <2119212+jsoref@users.noreply.github.com> * spelling: meaningful Signed-off-by: Josh Soref <2119212+jsoref@users.noreply.github.com> * spelling: mentored Signed-off-by: Josh Soref <2119212+jsoref@users.noreply.github.com> * spelling: monitoring Signed-off-by: Josh Soref <2119212+jsoref@users.noreply.github.com> * spelling: neither-nor Signed-off-by: Josh Soref <2119212+jsoref@users.noreply.github.com> * spelling: nonexistent Signed-off-by: Josh Soref <2119212+jsoref@users.noreply.github.com> * spelling: number greater than Signed-off-by: Josh Soref <2119212+jsoref@users.noreply.github.com> * spelling: of Signed-off-by: Josh Soref <2119212+jsoref@users.noreply.github.com> * spelling: optimization Signed-off-by: Josh Soref <2119212+jsoref@users.noreply.github.com> * spelling: originally Signed-off-by: Josh Soref <2119212+jsoref@users.noreply.github.com> * spelling: otherwise, Signed-off-by: Josh Soref <2119212+jsoref@users.noreply.github.com> * spelling: overriding Signed-off-by: Josh Soref <2119212+jsoref@users.noreply.github.com> * spelling: participating Signed-off-by: Josh Soref <2119212+jsoref@users.noreply.github.com> * spelling: performance Signed-off-by: Josh Soref <2119212+jsoref@users.noreply.github.com> * spelling: preexisting Signed-off-by: Josh Soref <2119212+jsoref@users.noreply.github.com> * spelling: prioritize Signed-off-by: Josh Soref <2119212+jsoref@users.noreply.github.com> * spelling: produces Signed-off-by: Josh Soref <2119212+jsoref@users.noreply.github.com> * spelling: programmatically Signed-off-by: Josh Soref <2119212+jsoref@users.noreply.github.com> * spelling: rate greater than Signed-off-by: Josh Soref <2119212+jsoref@users.noreply.github.com> * spelling: red hat Signed-off-by: Josh Soref <2119212+jsoref@users.noreply.github.com> * spelling: search Signed-off-by: Josh Soref <2119212+jsoref@users.noreply.github.com> * spelling: set up Signed-off-by: Josh Soref <2119212+jsoref@users.noreply.github.com> * spelling: show users Signed-off-by: Josh Soref <2119212+jsoref@users.noreply.github.com> * spelling: succeeded Signed-off-by: Josh Soref <2119212+jsoref@users.noreply.github.com> * spelling: successfully Signed-off-by: Josh Soref <2119212+jsoref@users.noreply.github.com> * spelling: sunset Signed-off-by: Josh Soref <2119212+jsoref@users.noreply.github.com> * spelling: syntax Signed-off-by: Josh Soref <2119212+jsoref@users.noreply.github.com> * spelling: table Signed-off-by: Josh Soref <2119212+jsoref@users.noreply.github.com> * spelling: that the scammers are impersonating Signed-off-by: Josh Soref <2119212+jsoref@users.noreply.github.com> * spelling: that the Signed-off-by: Josh Soref <2119212+jsoref@users.noreply.github.com> * spelling: that Signed-off-by: Josh Soref <2119212+jsoref@users.noreply.github.com> * spelling: the method implementation a bit Signed-off-by: Josh Soref <2119212+jsoref@users.noreply.github.com> * spelling: the moment, the Signed-off-by: Josh Soref <2119212+jsoref@users.noreply.github.com> * spelling: the project, the Signed-off-by: Josh Soref <2119212+jsoref@users.noreply.github.com> * spelling: the release, the Signed-off-by: Josh Soref <2119212+jsoref@users.noreply.github.com> * spelling: the syntax is not trivial for some of the filters Signed-off-by: Josh Soref <2119212+jsoref@users.noreply.github.com> * spelling: the Signed-off-by: Josh Soref <2119212+jsoref@users.noreply.github.com> * spelling: to be a Signed-off-by: Josh Soref <2119212+jsoref@users.noreply.github.com> * spelling: to which methods are applied Signed-off-by: Josh Soref <2119212+jsoref@users.noreply.github.com> * spelling: tuned; more Signed-off-by: Josh Soref <2119212+jsoref@users.noreply.github.com> * spelling: unreducible Signed-off-by: Josh Soref <2119212+jsoref@users.noreply.github.com> * spelling: waiting Signed-off-by: Josh Soref <2119212+jsoref@users.noreply.github.com> * spelling: whirlwind Signed-off-by: Josh Soref <2119212+jsoref@users.noreply.github.com> * spelling: workaround Signed-off-by: Josh Soref <2119212+jsoref@users.noreply.github.com> * spelling: workload Signed-off-by: Josh Soref <2119212+jsoref@users.noreply.github.com> * spelling: youtube Signed-off-by: Josh Soref <2119212+jsoref@users.noreply.github.com> --------- Signed-off-by: Josh Soref <2119212+jsoref@users.noreply.github.com>
1 parent 6a4d537 commit 319fc9c

File tree

111 files changed

+189
-190
lines changed

Some content is hidden

Large Commits have some content hidden by default. Use the searchbox below for content that may be hidden.

111 files changed

+189
-190
lines changed

_downloads/2014-02-04-2.10.4-RC2.md

Lines changed: 2 additions & 2 deletions
Original file line numberDiff line numberDiff line change
@@ -1,9 +1,9 @@
11
---
22
title: Scala 2.10.4-RC2
3-
start: 4 Februrary 2014
3+
start: 4 February 2014
44
layout: downloadpage
55
release_version: 2.10.4-RC2
6-
release_date: "Feburary 4, 2014"
6+
release_date: "February 4, 2014"
77
show_resources: "true"
88
permalink: /download/2.10.4-RC2.html
99
requirements: "This Scala software distribution can be installed on any Unix-like or Windows system. It requires the Java runtime version 1.6 or later, which can be downloaded <a href='https://www.java.com/'>here</a>."

_events/2017-10-26-lambda-world.md

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -3,7 +3,7 @@ category: event
33
title: Lambda World
44
logo: /resources/img/lambda-world-2.png
55
location: Cádiz, Spain
6-
description: Lambda World is the largest functional programming event in Spain and orients around various FP languages such as Scala, Kotlin, Java, Haskell, Elm, Clojure, and Javascript
6+
description: Lambda World is the largest functional programming event in Spain and orients around various FP languages such as Scala, Kotlin, Java, Haskell, Elm, Clojure, and JavaScript
77
start: 26 October 2017
88
end: 27 October 2017
99
link-out: https://www.lambda.world/

_includes/footer.html

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -6,7 +6,7 @@
66
<li><h3>{{item.title}}</h3></li>
77
{% for link in item.links %}
88
{% if link.title == "Mastodon" %}
9-
<!-- special case Manstodon to validate with rel="me" -->
9+
<!-- special case Mastodon to validate with rel="me" -->
1010
<li><a rel="me" href="{{link.url}}">{{link.title}}</a></li>
1111
{% else %}
1212
<li><a href="{{link.url}}">{{link.title}}</a></li>

_includes/navbar-inner.html

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -2,7 +2,7 @@
22
{% include alert-banner.html message_id='disabled' message=site.data.messages.scam-banner %}
33
<div class="wrap">
44
<nav class="navigation" role="menu">
5-
<a href="/" class="navigation-bdand">
5+
<a href="/" class="navigation-band">
66
<img src="/resources/img/frontpage/scala-logo-white@2x.png" alt="">
77
</a>
88
<div class="navigation-panel-button">

_includes/online-courses.html

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -6,7 +6,7 @@ <h2><span>Online Courses</span></h2>
66

77
{% comment %}
88
We're going to follow the next ordering for the online courses:
9-
1- First we'll show those items that belong to an specific specialization (i.e.: Scala's progfun in Coursera). Those will be ordered alphabetically by title and each item under the specialization by the `specialization-order` tag in each one.
9+
1- First we'll show those items that belong to a specific specialization (i.e.: Scala's progfun in Coursera). Those will be ordered alphabetically by title and each item under the specialization by the `specialization-order` tag in each one.
1010
2- After those, courses that don't belong to any specific specialization.
1111
We'll only show those courses that are not finished yet.
1212
{% endcomment %}

_layouts/frontpage.html

Lines changed: 2 additions & 2 deletions
Original file line numberDiff line numberDiff line change
@@ -21,10 +21,10 @@
2121
<div class="wrap">
2222
<!-- Navigation -->
2323
<nav class="navigation" role="menu">
24-
<div class="navigation-bdand-vfill-lg hide-lg">
24+
<div class="navigation-band-vfill-lg hide-lg">
2525
<!-- spacer to substitute for hidden logo, disappears below the large breakpoint -->
2626
</div>
27-
<a href="/" class="navigation-bdand show-lg">
27+
<a href="/" class="navigation-band show-lg">
2828
<!-- show standard nav logo below the large breakpoint -->
2929
<img src="/resources/img/frontpage/scala-logo-white@2x.png" alt=""/>
3030
</a>

_online_courses/big-data-analysis-with-scala-and-spark.md

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -17,4 +17,4 @@ Learning Outcomes. By the end of this course you will be able to:
1717
- express algorithms for data analysis in a functional style,
1818
- recognize how to avoid shuffles and recomputation in Spark,
1919

20-
Recommended background: You should have at least one year programming experience. Proficiency with Java or C# is ideal, but experience with other languages such as C/C++, Python, Javascript or Ruby is also sufficient. You should have some familiarity using the command line. This course is intended to be taken after Parallel Programming: https://www.coursera.org/learn/parprog1.
20+
Recommended background: You should have at least one year programming experience. Proficiency with Java or C# is ideal, but experience with other languages such as C/C++, Python, JavaScript or Ruby is also sufficient. You should have some familiarity using the command line. This course is intended to be taken after Parallel Programming: https://www.coursera.org/learn/parprog1.

_online_courses/functional_program_design_in_scala.md

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -21,4 +21,4 @@ Learning Outcomes. By the end of this course you will be able to:
2121
functions and state,
2222
- write simple functional reactive applications.
2323

24-
Recommended background: You should have at least one year programming experience. Proficiency with Java or C# is ideal, but experience with other languages such as C/C++, Python, Javascript or Ruby is also sufficient. You should have some familiarity using the command line. This course is intended to be taken after Functional Programming Principles in Scala: https://www.coursera.org/learn/scala-functional-programming.
24+
Recommended background: You should have at least one year programming experience. Proficiency with Java or C# is ideal, but experience with other languages such as C/C++, Python, JavaScript or Ruby is also sufficient. You should have some familiarity using the command line. This course is intended to be taken after Functional Programming Principles in Scala: https://www.coursera.org/learn/scala-functional-programming.

_online_courses/functional_programming_principles_scala.md

Lines changed: 2 additions & 2 deletions
Original file line numberDiff line numberDiff line change
@@ -8,7 +8,7 @@ paid: false
88
showDate: false
99
---
1010

11-
Functional programming is becoming increasingly widespread in industry. This trend is driven by the adoption of Scala as the main programming language for many applications. Scala fuses functional and object-oriented programming in a practical package. It interoperates seamlessly with both Java and Javascript. Scala is the implementation language of many important frameworks, including Apache Spark, Kafka, and Akka. It provides the core infrastructure for sites such as X, Tumblr and Coursera.
11+
Functional programming is becoming increasingly widespread in industry. This trend is driven by the adoption of Scala as the main programming language for many applications. Scala fuses functional and object-oriented programming in a practical package. It interoperates seamlessly with both Java and JavaScript. Scala is the implementation language of many important frameworks, including Apache Spark, Kafka, and Akka. It provides the core infrastructure for sites such as X, Tumblr and Coursera.
1212

1313
In this course you will discover the elements of the functional programming style and learn how to apply them usefully in your daily programming tasks. You will also develop a solid foundation for reasoning about functional programs, by touching upon proofs of invariants and the tracing of execution symbolically.
1414

@@ -24,4 +24,4 @@ Learning Outcomes. By the end of this course you will be able to:
2424
- reason about properties of functions,
2525
- understand generic types for functional programs
2626

27-
Recommended background: You should have at least one year programming experience. Proficiency with Java or C# is ideal, but experience with other languages such as C/C++, Python, Javascript or Ruby is also sufficient. You should have some familiarity using the command line.
27+
Recommended background: You should have at least one year programming experience. Proficiency with Java or C# is ideal, but experience with other languages such as C/C++, Python, JavaScript or Ruby is also sufficient. You should have some familiarity using the command line.

_online_courses/parallel_programming.md

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -17,4 +17,4 @@ Learning Outcomes. By the end of this course you will be able to:
1717
- competently microbenchmark parallel code,
1818
- write programs that effectively use parallel collections to achieve performance
1919

20-
Recommended background: You should have at least one year programming experience. Proficiency with Java or C# is ideal, but experience with other languages such as C/C++, Python, Javascript or Ruby is also sufficient. You should have some familiarity using the command line. This course is intended to be taken after Functional Program Design in Scala: https://www.coursera.org/learn/scala-functional-program-design.
20+
Recommended background: You should have at least one year programming experience. Proficiency with Java or C# is ideal, but experience with other languages such as C/C++, Python, JavaScript or Ruby is also sufficient. You should have some familiarity using the command line. This course is intended to be taken after Functional Program Design in Scala: https://www.coursera.org/learn/scala-functional-program-design.

0 commit comments

Comments
 (0)