fix docs

Author: Stepami

CONTRIBUTING.md

@@ -8,17 +8,16 @@ Contributions are welcomed! Here's a few things to know:
       - [Do not point fingers](#do-not-point-fingers)
       - [Provide code feedback based on evidence](#provide-code-feedback-based-on-evidence)
       - [Ask questions do not give answers](#ask-questions-do-not-give-answers)
-  - [HydraScript Contributor License Agreement](#hydrascript-contributor-license-agreement)
 
 ## Steps to Contributing
 
 Here are the basic steps to get started with your first contribution. Please reach out with any questions.
 1. Use [open issues](https://github.com/stepami/hydrascript/issues) to discuss the proposed changes. Create an issue describing changes if necessary to collect feedback. Also, please use provided labels to tag issues so everyone can easily sort issues of interest.
-1. [Fork the repo](https://help.github.com/articles/fork-a-repo/) in order if you want to make and test local changes.
-1. Create a new branch **from master** for the issue. We suggest prefixing the branch with type of contribution (`bugfix`/`feature`), your username and then a descriptive title: (e.g. `bugfix/user1/object-comparision` or `feature/user2/variable-initialization-check`)
-1. Make code changes.
-1. Ensure unit tests pass and code coverage minimum is satisfied.
-1. Create a pull request against **master** branch.
+2. [Fork the repo](https://help.github.com/articles/fork-a-repo/) in order if you want to make and test local changes.
+3. Create a new branch **from master** for the issue. We suggest prefixing the branch with type of contribution (`bugfix`/`feature`), your username and then a descriptive title: (e.g. `bugfix/user1/object-comparision` or `feature/user2/variable-initialization-check`)
+4. Make code changes.
+5. Ensure unit tests pass and code coverage minimum is satisfied.
+6. Create a pull request against **master** branch.
 
 ## Code of conduct
 
@@ -54,10 +53,4 @@ Try to be empathic.
 * Would it make more sense if ...?
 * Have you considered this ... ?
 
-</details>
-
-## HydraScript Contributor License Agreement
-
-Most contributions require you to agree to a Contributor License Agreement (CLA) declaring that you have the right to, and actually do, grant us the rights to use your contribution.
-
-When you submit a pull request, a CLA-bot will automatically determine whether you need to provide a CLA and decorate the PR appropriately (e.g., label, comment). Simply follow the instructions provided by the bot. You will only need to do this once in this repo.
+</details>

SECURITY.md

@@ -3,7 +3,7 @@
 ## Supported Versions
 
 | Version | Supported          |
-| ------- | ------------------ |
+|---------|--------------------|
 | > 1.0   | :white_check_mark: |
 
 ## Reporting a Vulnerability
@@ -15,4 +15,4 @@ Security issues and bugs should be reported privately via email to stepami@mail.
 ## When Should I Report a Vulnerability?
 
 - You think you discovered a potential security vulnerability
-- You are unsure how a vulnerability affects YTsaurus
+- You are unsure how a vulnerability affects HydraScript