diff --git a/README.md b/README.md
index aaefb28..9cf854b 100644
--- a/README.md
+++ b/README.md
@@ -21,7 +21,7 @@ Hub of all open-source third-party static analyzers supported by DeepSource. Usa
 To add a new analyzer, create a new directory with the analyzer shortcode under the `analyzers` folder.
 The following are very important to sync analyzers with DeepSource:
 
-1. `.deepsource/analyzer` directory under `analyzer/<analyzer-shortcode>` directory.
+1. `.deepsource/analyzer` directory under `analyzers/<analyzer-shortcode>` directory.
 
    a. It should contain an `analyzer.toml` file with the following fields:
 
@@ -32,11 +32,11 @@ The following are very important to sync analyzers with DeepSource:
    - `tool_latest_version`: Analyzer's latest version for which issues are synced on DeepSource.
    - `description`: A readable descrioption for this analyzer.
 
-   b. It should contain am `example.toml` file with a snippet to activate this analyzer in `.deepsource.toml` config.
+   b. It should contain an `example_config.toml` file with a snippet to activate this analyzer in `.deepsource.toml` config.
 
    c. `logo.svg` file.
 
-2. `.deepsource/issues` directory. This contains all issues detected by the analyzer. Each issue's filemane should be `<issue-shortcode>.toml` or `<issue-shortcode.md>` with the following fields:
+2. `.deepsource/issues` directory. This contains all issues detected by the analyzer. Each issue's filename should be `<issue-shortcode>.toml` or `<issue-shortcode.md>` with the following fields:
 
    - `title`: Title of the issue. No periods are allowed in the title.
    - `category`: Category of the issue. Allowed values are: "bug-risk", "doc", "style", "antipattern", "coverage", "security", "performance", "typecheck", and, "secrets".
@@ -51,7 +51,7 @@ Each file should be names as `<provider>.<extention>`. Example: `github.yml`, `c
 
 4. `utils` directory:
 
-It should contain all the utilities required for the analyzer like issue genrator, issue-map, etc.
+It should contain all the utilities required for the analyzer like issue generator, issue-map, etc.
 For example, please check out `analyzers/kube-linter/utils`.
 
 5. Add a sample sarif report from the analyzer in `tests/fixtures` directory. The file should be named as `<analyzer-shortcode>.sarif`.