Fix typos in www-gitlab-com entire project

source/topics/serverless/index.html.haml

@@ -34,7 +34,7 @@ extra_js:
     :markdown
       ## Serverless business logic
-      Every application uses servers at some point. The term Serverless emphasizes an architecture and service model where the developers need not concern themselves with infrastructre and instead can focus on the business logic of thier appliction. Serverless is the next evolution of architectural design from monolith, to [microservices](/topics/microservices/), to functions as Adrian Cockcroft explains in this video:
+      Every application uses servers at some point. The term Serverless emphasizes an architecture and service model where the developers need not concern themselves with infrastructure and instead can focus on the business logic of their appliction. Serverless is the next evolution of architectural design from monolith, to [microservices](/topics/microservices/), to functions as Adrian Cockcroft explains in this video:
     %p
       <iframe width="853" height="480" src="https://www.youtube.com/embed/aBcG57Gw9k0" frameborder="0" allow="autoplay; encrypted-media" allowfullscreen></iframe>
@@ -45,17 +45,17 @@ extra_js:
       ![monolith vs microservices](/images/serverless/serverless-header.svg)
-      Often serverless and FaaS are treated as interchangable terms, but this this isn't really accurate. Serverless is an overarching architectural pattern that makes use of a FaaS along with other cloud managed services. FaaS is a specific type of service such as AWS Lambda, Google Cloud Functions, and Azure Functions, that enables developers to deploy functions.
+      Often serverless and FaaS are treated as interchangeable terms, but this this isn't really accurate. Serverless is an overarching architectural pattern that makes use of a FaaS along with other cloud managed services. FaaS is a specific type of service such as AWS Lambda, Google Cloud Functions, and Azure Functions, that enables developers to deploy functions.
   .content.tile
     :markdown
       ## Attributes of serverless
       1. Small, descrete units of code. Often services written using serverless architecture are comprised of a single function.
-      2. Event-based execution. The infrastructure needed to run a function doesn't exist until a function is triggered. Once an event is recieved an ephemeral compute environment is created to execute that request. The environment may be destroyed immediately, or more commonly stays active for a short period of time, commonly 5 minutes.
+      2. Event-based execution. The infrastructure needed to run a function doesn't exist until a function is triggered. Once an event is received an ephemeral compute environment is created to execute that request. The environment may be destroyed immediately, or more commonly stays active for a short period of time, commonly 5 minutes.
       3. Scale to zero. Once a function stops receiving requests the infrastructure is taken down and completely stops running. This saves on cost since the infrastructure only runs when there is usage. If there's no usage, the environment scales down to zero.
       4. Scale to infinity. The FaaS takes care of monitoring load and creating additional instances when needed, in theory, up to infinity. This virtually eliminates the need for developers to think about scale as they design applications. A single deployed function can handle one or one billion requests without any change to the code.
-      5. Use of managed services. Often serverless architectures make use of cloud provided services for elements of thier application that provide non-differentiated heavy lifting such as file storage, databases, queueing, etc. For example, Google's Firebase is popular in the serverless community as a database and state management service that connects to other Google services like Cloud Functions.
+      5. Use of managed services. Often serverless architectures make use of cloud provided services for elements of their application that provide non-differentiated heavy lifting such as file storage, databases, queueing, etc. For example, Google's Firebase is popular in the serverless community as a database and state management service that connects to other Google services like Cloud Functions.
   .content.tile
     :markdown
@@ -76,7 +76,7 @@ extra_js:
     :markdown
       ## Business value of serverless
-      1. Faster pace of innovation. Developer productivty increases when they can focus solely on business logic.
+      1. Faster pace of innovation. Developer productivity increases when they can focus solely on business logic.
       1. Greater stability/resiliency (less loss of revenue due to downtime)
       1. Greater scale, the software is able to keep up with business demand
       1. Lower costs. Since compute is only billed when a service is active, servless provides tremendous cost savings vs always-on infrastructure.

spec/homepage/team/member_spec.rb

@@ -192,7 +192,7 @@ describe Gitlab::Homepage::Team::Member do
     end
   end
-  describe 'middleman compatibile delegated data sources' do
+  describe 'middleman compatible delegated data sources' do
     subject { described_class.new('name' => 'grzesiek') }
     context 'when data key exists' do