Merge branch 'main' of https://github.com/allegro/blog

CONTRIBUTING.md

@@ -6,7 +6,7 @@ Please also have a look at [README.md](README.md) for a general introduction to
 # Before you begin
 
 * If in doubt whether your idea for a post is right for the blog, [get in touch with the editors on Slack](README.md#where-to-get-help)
-* All texts should be in English. Editors will be happy to help with grammar and spelling. In special cases, we can arrange for our company professional
+* All texts should be in English. Editors will be happy to help with grammar and spelling. In special cases, we can arrange for our company's professional
   translators to help with translating the whole text.
 * Read a few recent posts in order to get familiar with subjects and style.
 * The post should be comprehensible for:
@@ -138,7 +138,7 @@ Text lines should not be longer than **160 characters**, for the same reason as
 
 ## Code formatting
 
-Inlined code fragments such as `user_id` should be wrapped  with backtick quotes (`).
+Inlined code fragments such as `user_id` should be wrapped with backtick quotes (`).
 
 Code blocks should be formatted with syntax highlighting,
 using GitHub style syntax -  <code>```language</code>
@@ -171,7 +171,7 @@ If this is your first post, prepare your Bio (see above for details).
 
 ### Rendering on local machine
 
-If you're Mac user and you haven't installed Ruby yourself, then you could perform following steps:
+If you're Mac user and you haven't installed Ruby yourself, then you could perform the following steps:
 * `brew install ruby`
 * add `export PATH="/usr/local/opt/ruby/bin:$PATH"` into your `.bashrc`/`.zshrc`
 

README.md

@@ -7,7 +7,7 @@ We write for smart people who are good at telling genuinely interesting and usef
 The blog is hosted at [blog.allegro.tech](https://blog.allegro.tech/). We also cooperate with Allegro tech hub page [allegro.tech](https://allegro.tech/).
 
 Goals:
-* Creating a technical blog valuable for the community. We focus on development and devops.
+* Creating a technical blog valuable for the community. We focus on development and DevOps.
 * Letting the community know about events we organize or take part in.
 * Maintaining the image of Allegro as a technical leader and a place where great engineers work.
 * Highlighting our achievements but also describing our failures, for example by publishing outage postmortems.
@@ -16,7 +16,7 @@ Rules:
 * We strive for high-quality posts (in both content and style).
 * We publish in English.
 * Posts must go through a review process.
-* Blog’s editors decide on the order posts are published. They can also reject posts deemed not fit for the blog due to subject not matching the blog’s goals,
+* Blog’s editors decide on the order posts are published. They can also reject posts deemed not fit for the blog due to subjects not matching the blog’s goals,
   low quality, inappropriate content, not following company policies, etc. In practice, this happens only very rarely.
 
 # Where to get help