fixed markdown issues

halyph · Aug 13, 2024 · 791b190 · 791b190
1 parent c792288
commit 791b190
Show file tree

Hide file tree

Showing 7 changed files with 26 additions and 24 deletions.
diff --git a/docs/blog/2015/2015-03-17-how-to-download-jars-from-maven-central.md b/docs/blog/2015/2015-03-17-how-to-download-jars-from-maven-central.md
@@ -11,7 +11,8 @@ Assume that we'd like to download `spark-core` library (`groupId=com.sparkjava,
 
 Here is there variants for lib download:
 
-```bash Download library with all dependencies
+```bash 
+# Download library with all dependencies
 # Specify repoUrl (it's optional)
 mvn dependency:get -DrepoUrl=http://download.java.net/maven/2/ -DgroupId=com.sparkjava -DartifactId=spark-core -Dversion=2.1
 
@@ -24,7 +25,8 @@ mvn dependency:get -Dartifact=com.sparkjava:spark-core:2.1
 
 Now we need to copy just downloaded artifacts in our working directory:
 
-```bash Copy jars from local maven repo
+```bash 
+# Copy jars from local maven repo
 mvn dependency:copy-dependencies -f $HOME/.m2/repository/com/sparkjava/spark-core/2.1/spark-core-2.1.pom -DoutputDirectory=$(pwd)/lib
 # the previous command doesn't copy spark-core-x.x.jar, that's why we should copy it manually
 cp $HOME/.m2/repository/com/sparkjava/spark-core/2.1/spark-core-2.1.jar $(pwd)/lib
@@ -48,7 +50,8 @@ As you can see Ivy downloads approach is much simpler. The only cons (or pros, i
 
 Here I've decided to store [Evgeny's Goldin](http://makandracards.com/evgeny-goldin/5817-calling-ivy-from-groovy-or-java) code snippet as a reference for myself. Programmatic artifacts downloads is not a common operation. It's alway nice to know the general concept how it can be done. Especially when Ivy documentation is not very informative.
 
-```java Groovy snippet of calling Ivy
+```java
+// Groovy snippet of calling Ivy
 import org.apache.ivy.Ivy
 import org.apache.ivy.core.module.descriptor.DefaultDependencyDescriptor
 import org.apache.ivy.core.module.descriptor.DefaultModuleDescriptor

diff --git a/docs/blog/2016/2016-11-28-ruby-and-rails-the-bad-parts-by-volodymyr-melnyk.md b/docs/blog/2016/2016-11-28-ruby-and-rails-the-bad-parts-by-volodymyr-melnyk.md
@@ -6,22 +6,21 @@
 - [Bad](#bad)
   - [Ruby isn’t Static- typed](#ruby-isnt-static--typed)
   - [Ruby has an unclear concept of Module](#ruby-has-an-unclear-concept-of-module)
-  - [Proc & Lambda](#proc--lambda)
+  - [Proc and Lambda](#proc-and-lambda)
   - [Ruby Standard Library is a ghetto](#ruby-standard-library-is-a-ghetto)
     - [Abbrev](#abbrev)
     - [Delegator](#delegator)
     - [Alternate syntax](#alternate-syntax)
-    - [`&&` versus `and`](#versus-and)
-    - [`||` versus `or`](#versus-or)
+    - [`&&` versus `and`](#-versus-and)
+    - [`||` versus `or`](#-versus-or)
   - [Values against expressions You should know!](#values-against-expressions-you-should-know)
   - [Boolean Algebra Fail](#boolean-algebra-fail)
   - [Ruby is not that strongly-typed language.](#ruby-is-not-that-strongly-typed-language)
   - [`nil`](#nil)
 
 ## References
 
-These notes are compilled from:
-* https://speakerdeck.com/egoholic/ruby-and-rails-the-bad-parts
+These notes are compiled from https://speakerdeck.com/egoholic/ruby-and-rails-the-bad-parts.
 
 ## Good Parts
 
@@ -68,7 +67,7 @@ C.singleton_class.ancestors
 #]
 ```
 
-### Proc & Lambda
+### Proc and Lambda
 
 In Ruby we have a `Proc` class and two types of its instances (it’s strange), but actually we need only one of them (as for me, I prefer lambdas).
 

diff --git a/docs/blog/2016/2016-11-29-the-bad-parts-by-bozhidar-batsov.md b/docs/blog/2016/2016-11-29-the-bad-parts-by-bozhidar-batsov.md
@@ -2,7 +2,7 @@
 > | ruby |
 
 - [Reference](#reference)
-- [The Problem :-)](#the-problem)
+- [The Problem](#the-problem)
 - [The Real Problem](#the-real-problem)
   - [Problems with the Runtime](#problems-with-the-runtime)
   - [Rubygems and Bundler](#rubygems-and-bundler)
@@ -22,7 +22,7 @@ These notes are compilled from: https://speakerdeck.com/bbatsov/ruby-the-bad-par
 - [Ruby: The Bad Parts by Bozhidar Batsov](https://speakerdeck.com/bbatsov/ruby-the-bad-parts)
 - [Ruby 4.0: To Infinity and Beyond (Athens Ruby Meetup) by Bozhidar Batsov](https://speakerdeck.com/bbatsov/ruby-4-dot-0-to-infinity-and-beyond-athens-ruby-meetup)
 
-## The Problem :-)
+## The Problem
 
 - Ruby is object-oriented
 - Ruby is dynamically typed

diff --git a/docs/blog/2016/2016-11-30-python-vs-ruby-battle-to-the-death-by-gary-bernhardt.md b/docs/blog/2016/2016-11-30-python-vs-ruby-battle-to-the-death-by-gary-bernhardt.md
@@ -5,12 +5,12 @@
 - [I. Ruby Complaints](#i-ruby-complaints)
   - [The Zen of Python (PEP-20)](#the-zen-of-python-pep-20)
     - [8. Special cases aren't special enough to break the rules](#8-special-cases-arent-special-enough-to-break-the-rules)
-    - [13. There should be one-- and preferably only one --obvious way to do it](#13-there-should-be-one---and-preferably-only-one---obvious-way-to-do-it)
+    - [13. There should be one and preferably only one obvious way to do it](#13-there-should-be-one-and-preferably-only-one-obvious-way-to-do-it)
     - [16. Although never is often better than *right* now](#16-although-never-is-often-better-than-right-now)
     - [17. If the implementation is hard to explain, it's a bad idea](#17-if-the-implementation-is-hard-to-explain-its-a-bad-idea)
       - [Ruby Grammar](#ruby-grammar)
       - [Python Grammar](#python-grammar)
-    - [19. Namespaces are one honking great idea -- let's do more of those!](#19-namespaces-are-one-honking-great-idea----lets-do-more-of-those)
+    - [19. Namespaces are one honking great idea - let's do more of those!](#19-namespaces-are-one-honking-great-idea---lets-do-more-of-those)
 - [II. Ruby Praise](#ii-ruby-praise)
   - [Composability](#composability)
     - [RSpec](#rspec)
@@ -63,7 +63,7 @@ NoMethodError: undefined method `x' for main:Object
 5
 ```
 
-#### 13. There should be one-- and preferably only one --obvious way to do it
+#### 13. There should be one and preferably only one obvious way to do it
 
 > *Yukihiro Matsumoto*: Ruby inherited the Perl philosophy of having more than one way to do the same thing. I inherited that philosophy from Larry Wall, who is my hero actually. *I want to make Ruby users free. I want to give them the freedom to choose. People are different. People choose different criteria. But if there is a better way among many alternatives, I want to encourage that way by making it comfortable. So that's what I've tried to do. Maybe Python code is a bit more readable. Everyone can write the same style of Python code, so it can be easier to read, maybe. But the difference from one person to the next is so big, providing only one way is little help even if you're using Python, I think. I'd rather provide many ways if it's possible, but encourage or guide users to choose a better way if it's possible.*
 - Reference: [The Philosophy of Ruby.A Conversation with Yukihiro Matsumoto, Part I by Bill Venners. September 29, 2003](http://www.artima.com/intv/ruby3.html)
@@ -102,7 +102,7 @@ Now
 
 ![pygr.jpg](2016-11-30-python-vs-ruby-battle-to-the-death-by-gary-bernhardt/pygr.jpg)
 
-#### 19. Namespaces are one honking great idea -- let's do more of those!
+#### 19. Namespaces are one honking great idea - let's do more of those!
 
 
 ```ruby

diff --git a/docs/blog/2018/2018-12-20-scala-for-compr.md b/docs/blog/2018/2018-12-20-scala-for-compr.md
@@ -6,7 +6,7 @@ This is a complete copy of **Josh Suereth** & **Dick Wall** talk on *Scala World
 Actually, I have found github repository with Jupiter notebooks. But, I don't like this format and decided to store these notes here.
 
 - [References](#references)
-- [01 - For "loops"](#01---for-%22loops%22)
+- [01 - For "loops"](#01---for-loops)
 - [02 - For with yield](#02---for-with-yield)
 - [03 - Options](#03---options)
 - [04 - Future](#04---future)
@@ -18,7 +18,7 @@ Actually, I have found github repository with Jupiter notebooks. But, I don't li
 - [10 - Other Monads](#10---other-monads)
 - [11 - `scala-arm`](#11---scala-arm)
 - [12 - Monads don't mix](#12---monads-dont-mix)
-- [13 - `Emm & M[_]`](#13---emm--m)
+- [13 - `Emm & M[_]`](#13---emm--m_)
 - [14 - How to Option Your Futures](#14---how-to-option-your-futures)
 - [15 - Sink](#15---sink)
 
@@ -1513,7 +1513,7 @@ fListONums: Future[List[Int]] = Success(List(1, 2, 3, 4, 5))
 res4_2: Future[List[Int]] = Success(List(1, 4, 9, 16, 25))
 ```
 
-## 13 - `Emm  & M[_]`
+## 13 - `Emm & M[_]`
 
 ### 13.01<!-- omit in toc -->
 

diff --git a/docs/blog/2019/2019-02-27-lambda-days.md b/docs/blog/2019/2019-02-27-lambda-days.md
@@ -9,16 +9,16 @@ Here is the list of talks I've attended (some talks have been excluded from this
 
 - [Day 1 (February 21, 2019)](#day-1-february-21-2019)
   - [1 - Keynote: F# Code I Love by Don Syme (*F# Language Designer*)](#1---keynote-f-code-i-love-by-don-syme-f-language-designer)
-  - [2 - FP Design Patterns in Micro-Service Inter-Process Communication by Viačeslav Pozdniakov](#2---fp-design-patterns-in-micro-service-inter-process-communication-by-via%C4%8Deslav-pozdniakov)
+  - [2 - FP Design Patterns in Micro-Service Inter-Process Communication by Viaceslav Pozdniakov](#2---fp-design-patterns-in-micro-service-inter-process-communication-by-viaceslav-pozdniakov)
   - [3 - Empowering the Quantum revolution with Q# by John Azariah](#3---empowering-the-quantum-revolution-with-q-by-john-azariah)
-  - [From Haskell to C#, A story of culture shocks and happy reunions by Øystein Kolsrud](#from-haskell-to-c-a-story-of-culture-shocks-and-happy-reunions-by-%C3%B8ystein-kolsrud)
+  - [From Haskell to C#, A story of culture shocks and happy reunions by Øystein Kolsrud](#from-haskell-to-c-a-story-of-culture-shocks-and-happy-reunions-by-øystein-kolsrud)
   - [4 - Elm, Fable, and the Practical Implications of Programming Language Philosophy by Michael Newton](#4---elm-fable-and-the-practical-implications-of-programming-language-philosophy-by-michael-newton)
   - [5 - One year of using F# in production at SBTech by Anton Moldovan](#5---one-year-of-using-f-in-production-at-sbtech-by-anton-moldovan)
   - [6 - (Dys)functional DDD by Jarek Ratajski](#6---dysfunctional-ddd-by-jarek-ratajski)
 - [Day 2 (February 22, 2019)](#day-2-february-22-2019)
   - [7 - Scala superpowers: effortless domain driven design by Bartosz Mikulski](#7---scala-superpowers-effortless-domain-driven-design-by-bartosz-mikulski)
   - [8 - Effective Data Engineering using higher kinded types by Animesh Kumar](#8---effective-data-engineering-using-higher-kinded-types-by-animesh-kumar)
-  - [9 - Fast & Functional by Michał Płachta](#9---fast--functional-by-micha%C5%82-p%C5%82achta)
+  - [9 - Fast \& Functional by Michał Płachta](#9---fast--functional-by-michał-płachta)
   - [10 - Behind collaborative text editing by Bartosz Sypytkowski](#10---behind-collaborative-text-editing-by-bartosz-sypytkowski)
   - [11 - Teaching Functional Programming by Michael Sperber](#11---teaching-functional-programming-by-michael-sperber)
 
@@ -33,7 +33,7 @@ Here is the list of talks I've attended (some talks have been excluded from this
 
 The most interesting for me was this paper: [The Early History of F# (HOPL IV - first draft)](https://fsharp.org/history/hopl-draft-1.pdf). This paper has 36 pages, you will like it if you like **IT history**.
 
-### 2 - FP Design Patterns in Micro-Service Inter-Process Communication by [Viačeslav Pozdniakov](https://github.com/vipo)
+### 2 - FP Design Patterns in Micro-Service Inter-Process Communication by [Viaceslav Pozdniakov](https://github.com/vipo)
 
 > Design of correct and yet simple inter-process communication in micro-service architecture is a tough thing to do: communication protocols might be sync or async, some APIs use request/response model while others use streaming and so on. In this talk we will discuss which micro-service IPC design problems we (Wix.com) faced and how we solve them using FP building blocks: monads, semigroups, etc. Obviously, introduction of FP design patterns at our scale (>500 developers) is a huge effort, so we will also discuss an execution process of such changes.
 

diff --git a/docs/blog/2019/2019-09-30-python-bad-practices.md b/docs/blog/2019/2019-09-30-python-bad-practices.md
@@ -29,7 +29,7 @@ I've been using Python as scripting language on a non-regular basis. It means I
   - [3.1 - Misunderstanding Python scope rules](#31---misunderstanding-python-scope-rules)
   - [3.2 - Confusing how Python binds variables in closures](#32---confusing-how-python-binds-variables-in-closures)
   - [3.3 - Variable naming](#33---variable-naming)
-  - [3.4  - Identifying variable types with prefixes](#34----identifying-variable-types-with-prefixes)
+  - [3.4 - Identifying variable types with prefixes](#34---identifying-variable-types-with-prefixes)
 - [4 - Classes](#4---classes)
   - [4.1 - Implementing Java-style getters and setters](#41---implementing-java-style-getters-and-setters)
   - [4.2 - Using property setters as action methods](#42---using-property-setters-as-action-methods)
@@ -719,7 +719,7 @@ id_ = 34
 
 ---
 
-### 3.4  - Identifying variable types with prefixes
+### 3.4 - Identifying variable types with prefixes
 
 Ref: [[6](#original-sources)]