Fix typos (#246)

Author: Volosh1n

slides/api.markdown

@@ -45,7 +45,7 @@ Let's take a look at some of the things that Rails provides out of the box that
 
 # Versioning
 
-If you are writing a consistent API which will be consumed by multiple clients then it is the best practise to separate out the API under a namespace.
+If you are writing a consistent API which will be consumed by multiple clients then it is the best practice to separate out the API under a namespace.
 
 API versioning lets your API to be backwards compatible.
 
@@ -167,7 +167,7 @@ end
 
 Serialization is the process of translating data structures or object state into a format that can be stored
 
-Rails serializes the object passed into the required format. What if you want to customise the JSON output? Like Remove the root element, Add custom attributes or Adding `has_many` relations? How do you acheive this?
+Rails serializes the object passed into the required format. What if you want to customize the JSON output? Like Remove the root element, Add custom attributes or Adding `has_many` relations? How do you achieve this?
 
 --
 
@@ -255,7 +255,7 @@ rails g resource comment content:text user:references post:references
 
 When we try to render out a model in a JSON format active model serializers automatically look for a serializer with the same name which is used to fetch data.
 
-So render `ruby json: Post.find(params[:id])` will automatically look for a serialzer named `PostSerializer`
+So render `ruby json: Post.find(params[:id])` will automatically look for a serializer named `PostSerializer`
 
 ```ruby
 class PostSerializer < ActiveModel::Serializer
@@ -273,7 +273,7 @@ render json: @post, serializer: MyAwesomeSerializer
 
 ## Customizing the format
 
-Since Active Model Serailizers follow an object oriented approach customising the output is a piece of cake!
+Since Active Model Serailizers follow an object oriented approach customizing the output is a piece of cake!
 
 ```ruby
 class PostSerializer < ActiveModel::Serializer

slides/bdd.markdown

@@ -494,7 +494,7 @@ describe UsersController do
         expect(response).to redirect_to root_url
       end
 
-      it 'assings a success flash message' do
+      it 'assigns a success flash message' do
         expect(flash[:notice]).not_to be_nil
       end
 

slides/cancancan.markdown

@@ -271,7 +271,7 @@ spec/models/ability_spec.rb <!-- .element: class="filename" -->
 require 'cancan/matchers'
 
 describe Ability do
-  describe "abilities of loggined user" do
+  describe "abilities of logged in user" do
     subject { ability }
 
     let(:ability){ Ability.new(user) }
@@ -318,7 +318,7 @@ describe PostsController do
   end
 
   context '#new' do
-    context 'cancan doesnt allow :new' do
+    context 'cancan does not allow :new' do
       before do
         @ability.cannot :create, Post
         get :new
@@ -328,7 +328,7 @@ describe PostsController do
   end
 
   context '#show' do
-    context 'cancan doesnt allow :show' do
+    context 'cancan does not allow :show' do
       before do
         @ability.cannot :show, Post
         get :show, {id: @post.id}
@@ -338,7 +338,7 @@ describe PostsController do
   end
 
   context '#create' do
-    context 'cancan doesnt allow :create' do
+    context 'cancan does not allow :create' do
       before do
         @ability.cannot :create, Post
         post :create, {post: @post_attributes}
@@ -348,7 +348,7 @@ describe PostsController do
   end
 
   context '#update' do
-    context 'cancan doesnt allow :update' do
+    context 'cancan does not allow :update' do
       before do
         @ability.cannot :update, @post
         put :update, @post_attributes.merge(id: @post.id)
@@ -358,7 +358,7 @@ describe PostsController do
   end
 
   context '#destroy' do
-    context 'cancan doesnt allow :destroy' do
+    context 'cancan does not allow :destroy' do
       before do
         @ability.cannot :destroy, @post
         delete :destroy, id: @post.id

slides/circleci.markdown

@@ -126,9 +126,9 @@ The list of buil-in variables you can see [here](https://circleci.com/docs/2.0/e
 
 --
 
-## **Remember!** 
+## **Remember!**
 
-Do not add secrets or keys inside the `.circleci/config.yml` file. 
+Do not add secrets or keys inside the `.circleci/config.yml` file.
 
 The full text of `config.yml` is visible to developers with access to your project on CircleCI.
 
@@ -145,7 +145,7 @@ Store secrets or keys in [project](https://github.com/rubygarage/circledge/blob/
 
 **Caching** is one of the most effective ways to make jobs faster on CircleCI by reusing the data from expensive fetch operations from previous jobs.
 
-A good example is package dependency managers such as Yarn, Bundler, or Pip. With dependencies restored from a cache, commands like yarn install will only need to download new dependencies, if any, and not redownload everything on every build.
+A good example is package dependency managers such as Yarn, Bundler, or Pip. With dependencies restored from a cache, commands like yarn install will only need to download new dependencies, if any, and not re-download everything on every build.
 
 
 --
@@ -174,7 +174,7 @@ A good example is package dependency managers such as Yarn, Bundler, or Pip. Wit
 
 In order to clear the cache, you need to change the name of the key under which it is stored for example:
 ```yml
-  - v1-npm-deps-{{ checksum "package-lock.json" }} 
+  - v1-npm-deps-{{ checksum "package-lock.json" }}
 ```
 change to
 ```yml
@@ -192,7 +192,7 @@ change to
 - Use `cache` key for define names of you cache. example:
 
 ```yml
-caches: 
+caches:
   - &bundle_cache v1-repo-{{ checksum "Gemfile.lock"  }}
 
 commands:
@@ -211,7 +211,7 @@ commands:
 
 ![](/assets/images/circleci/steps.png)
 
-`Steps` are a collection of executable commands which are run during a job/command. 
+`Steps` are a collection of executable commands which are run during a job/command.
 
 If one step exit with code 1(failed), then the next ones will not be executed.
 
@@ -366,10 +366,10 @@ Currently, `store_artifacts` has two keys:
 .circleci/config.yml<!-- .element: class="filename" -->
 ```yml
 steps:
-  - run: 
+  - run:
       name: run specs
       command: |
-        bundle exec rspec 
+        bundle exec rspec
   - store_artifacts:
       path: ~/repo/coverage
       destination: coverage
@@ -389,17 +389,17 @@ After the completion of the job, you can see the artifacts in the tab 'Artifacts
 
 ## Overview
 
-To support the open source community, projects that are public on GitHub or Bitbucket receive three free build containers, for a total of four containers. 
+To support the open source community, projects that are public on GitHub or Bitbucket receive three free build containers, for a total of four containers.
 
 Only one container is available for private repositories
 
 --
 
 ## Only Build Pull Requests
 
-By default, CircleCI builds every commit from every branch. 
+By default, CircleCI builds every commit from every branch.
 
-This behavior may be too aggressive for open source projects, which often have significantly more commits than private projects. 
+This behavior may be too aggressive for open source projects, which often have significantly more commits than private projects.
 
 To change this setting, go to the Advanced Settings of your project and set the Only build pull requests option to On.
 
@@ -437,9 +437,9 @@ Often the best way to troubleshoot problems is to SSH into a job and inspect thi
 
 --
 
-If your project has a large number of tests, it will need more time to run them on one machine. 
+If your project has a large number of tests, it will need more time to run them on one machine.
 
-To reduce this time, you can run tests in parallel by spreading them across multiple machines. 
+To reduce this time, you can run tests in parallel by spreading them across multiple machines.
 
 ![](/assets/images/circleci/test_splitting.png)
 
@@ -468,9 +468,9 @@ jobs:
 
 --
 
-**CircleCI Orbs** are shareable packages of configuration elements, including jobs, commands, and executors. 
+**CircleCI Orbs** are shareable packages of configuration elements, including jobs, commands, and executors.
 
-CircleCI provides certified orbs, along with 3rd-party orbs authored by CircleCI partners. 
+CircleCI provides certified orbs, along with 3rd-party orbs authored by CircleCI partners.
 
 It is best practice to first evaluate whether any of these existing orbs will help you in your configuration workflow.
 
@@ -494,7 +494,7 @@ You can read about each of this features [here](https://github.com/rubygarage/ci
 
 Before using the orb, you need to read the documentation for use which can be found on the main page of the orb
 
-example of usage: 
+example of usage:
 
 .circleci/config.yml<!-- .element: class="filename" -->
 ```yml
@@ -566,29 +566,29 @@ executors:
           POSTGRES_USER: postgres
           POSTGRES_PASSWORD: postgres
 
-caches: 
+caches:
   - &bundle_cache v1-repo-{{ checksum "Gemfile.lock" }}
 
 commands:
   run_linters:
     description: command to start linters
     steps:
-      - run: 
+      - run:
           name: rubocop
           command: bundle exec rubocop
-      - run: 
+      - run:
           name: brakeman
           command: bundle exec brakeman -q
-      - run: 
+      - run:
           name: lol_dba
           command: bundle exec lol_dba db:find_indexes
-      - run: 
-          name: rails best prctices
+      - run:
+          name: rails best practices
           command: bundle exec rails_best_practices .
 
   run_specs:
     steps:
-      - run: 
+      - run:
           name: run specs
           command: |
             mkdir /tmp/test-results

slides/general/code_review.markdown

@@ -67,7 +67,7 @@ Code review ...
 
 ## Initiating
 
-- `Developer A` right after finishing his task pushes his code to VCS provider(Github, Github, e.t.c)
+- `Developer A` right after finishing his task pushes his code to VCS provider(Github, Gitlab, e.t.c)
 - `Developer A` knows all the GitFlow standards of his project/company and know how to name the branch and commits well
 - `Developer A` prepare the PR (correct title, description, milestones, labels, e.t.c, assignee)
 - `Developer A` check all the source code before setting reviewers

slides/graphql.markdown

@@ -189,7 +189,7 @@ This architecture will be the most common for new projects. In the setup, you ha
 
 --
 
-### 2. GraphQL server that is a ** thin layer in front of a number of third party or legacy systems** 
+### 2. GraphQL server that is a ** thin layer in front of a number of third party or legacy systems**
 
 GraphQL is used to **unify** these existing systems and hide their complexity. This way, new client applications can be developed that simply talk to the GraphQL server to fetch the data they need.
 
@@ -391,7 +391,7 @@ And response:
 
 ### Types
 
-#### Types describs data units in the system. There are such types as:
+#### Types describes data units in the system. There are such types as:
 
 - Default scalar types
 - Object types
@@ -1114,7 +1114,7 @@ GraphQL uses JSON format, which represents as text format, not as binary.
 You can send a file as base64 string or send a download link.
 
 ### - Incoming Webhooks
-You will need to add the REST endpoints to listen for events from services like Stripe. 
+You will need to add the REST endpoints to listen for events from services like Stripe.
 
 ---
 
@@ -1614,7 +1614,7 @@ query {
 
 --
 
-#### and we will recieve
+#### and we will receive
 
 ```json
 {
@@ -1657,7 +1657,7 @@ query {
 #### Expose **node** and **cursor** fields
 
 ### Node
-#### Nodes are items in a list. A node is usually an object in your schema. 
+#### Nodes are items in a list. A node is usually an object in your schema.
 
 --
 
@@ -2104,7 +2104,7 @@ https://github.com/rubygarage/graphql_meetup
 
 ---
 
-## Usefull links
+## Useful links
 
 https://www.howtographql.com/ - good graphql guides - different languages, frontend/backend
 

slides/models.markdown

@@ -1594,7 +1594,7 @@ end
 
 ---
 
-## Validates Assosiated
+## Validates Associated
 
 ```ruby
 class User < ApplicationRecord

slides/rails.markdown

@@ -18,7 +18,7 @@ do it, rather than requiring you to specify every little thing through endless c
 
 ---
 
-## Instaling Rails
+## Installing Rails
 
 ### Preparing environment
 

slides/refactoring-rails.markdown

@@ -560,7 +560,7 @@ class UsersController < ApplicationController
 
     respond_to do |format|
       if @user.save
-        format.html { redirect_to @user, notice: 'Signup successfull.' }
+        format.html { redirect_to @user, notice: 'Signup successful.' }
       else
         format.html { render new_signup_path }
       end
@@ -605,7 +605,7 @@ class UsersController < ApplicationController
 
     respond_to do |format|
       if @signup.save
-        format.html { redirect_to @signup.user, notice: 'Signup successfull.' }
+        format.html { redirect_to @signup.user, notice: 'Signup successful.' }
       else
         format.html { render new_signup_path }
       end

slides/refactoring-ruby.markdown

@@ -22,12 +22,12 @@ Refactoring is a systematic process of improving the quality of code without cha
 
 ---
 
-## Refactoring vs Optimisation vs Bugfixing
+## Refactoring vs Optimization vs Bugfixing
 
-| | Refactoring | Optimisation | Bugfixing |
+| | Refactoring | Optimization | Bugfixing |
 |-------------|-------------|-------------|-------------|
 | Making code clean | `true` | false | false |
-| Optimising performance | false | `true` | false |
+| Optimizing performance | false | `true` | false |
 | Changing code functionality | false | false | `true` |
 
 ---
@@ -67,7 +67,7 @@ When the development team has:
 
 1. Find code smells and document them
 2. Prioritize according to the following standards:
-  * importancy for business
+  * importance for business
   * frequency of usage of that piece of code
   * size of a code smell
   * coverage of specs and tests quality