fix typo

PhilippSalvisberg · PhilippSalvisberg · commit 73242feb87f8 · 2019-09-21T18:07:18.000+02:00
diff --git a/docs/1-introduction/introduction.md b/docs/1-introduction/introduction.md
@@ -84,4 +84,4 @@ For very controversial rules, we have started to include the reasoning either as
 
 Usually it is not helpful to open an issue on GitHub to request to change a highly controversial rule such as the one mentioned. For example, use 2 spaces instead of 3 spaces for an indentation. This leads to a discussion where the people in favor of 4 spaces start to argument as well. There is no right or wrong here. You just have to agree on a standard.
 
-More effective is to fork [this repository](https://github.com/Trivadis/plsql-and-sql-coding-guidelines) and amend the standards fit your needs/expectations.
+More effective is to fork [this repository](https://github.com/Trivadis/plsql-and-sql-coding-guidelines) and amend the standards to fit your needs/expectations.

Original file line number	Diff line number	Diff line change
`@@ -84,4 +84,4 @@ For very controversial rules, we have started to include the reasoning either as`
`84`	`84`
`85`	`85`	`Usually it is not helpful to open an issue on GitHub to request to change a highly controversial rule such as the one mentioned. For example, use 2 spaces instead of 3 spaces for an indentation. This leads to a discussion where the people in favor of 4 spaces start to argument as well. There is no right or wrong here. You just have to agree on a standard.`
`86`	`86`
`87`		`-More effective is to fork [this repository](https://github.com/Trivadis/plsql-and-sql-coding-guidelines) and amend the standards fit your needs/expectations.`
	`87`	`+More effective is to fork [this repository](https://github.com/Trivadis/plsql-and-sql-coding-guidelines) and amend the standards to fit your needs/expectations.`