<commit_before># Contributing to plex

## Thoughts on Style
Please follow the guidelines set out in the [Airbnb JavaScript ES5 Style Guide](https://github.com/airbnb/javascript/tree/master/es5).

Some examples of style rules to adhere to include, but are not limited to:
* use single quotes `''` for strings
* assign variables at the top of their scope
* use braces with all multi-line blocks (if-else statements
* use soft tabs set to 2 spaces
* place 1 space before the leading brace of a function body
* place 1 space before the opening parenthesis in control statements (if, while etc.)
* place no space before the argument list in function calls and declarations.
* end files with a single newline character
* leave a blank line after blocks and before the next statement
* use semicolons

## Git Forking Workflow
***
The Forking Workflow gives every developer working on the project a server-side repository, so that each contributor has not one, but two Git repositories: a private local one and a public server-side one. Developers push to their own server-side repositories, and only the project maintainer (i.e. scrum master) can push to the official repository.<commit_msg>[doc] fix spelling error in style subsection<commit_after># Contributing to plex

## Thoughts on Style
Please follow the guidelines set out in the [Airbnb JavaScript ES5 Style Guide](https://github.com/airbnb/javascript/tree/master/es5).

Some examples of style rules to adhere to include, but are not limited to:
* use single quotes `''` for strings
* assign variables at the top of their scope
* use braces with all multi-line blocks (if-else statements)
* use soft tabs set to 2 spaces
* place 1 space before the leading brace of a function body
* place 1 space before the opening parenthesis in control statements (if, while etc.)
* place no space before the argument list in function calls and declarations
* end files with a single newline character
* leave a blank line after blocks and before the next statement
* use semicolons

## Git Forking Workflow
***
The Forking Workflow gives every developer working on the project a server-side repository, so that each contributor has not one, but two Git repositories: a private local one and a public server-side one. Developers push to their own server-side repositories, and only the project maintainer (i.e. scrum master) can push to the official repository.
{'fraction_non_alphanumeric': 0.05252188411838266, 'fraction_numerical': 0.004168403501458941, 'mean_word_length': 4.607476635514018, 'pattern_counts': {'":': 0, '<': 3, '<?xml version=': 0, '>': 3, 'https://': 2, 'lorem ipsum': 0, 'www.': 0, 'xml': 0}, 'pii_count': 0, 'substrings_counts': 0, 'word_list_counts': {'cursed_substrings.json': 2, 'profanity_word_list.json': 0, 'sexual_word_list.json': 0, 'zh_pornsignals.json': 0}}
{'dir': 'git-commits-cleaned', 'id': '178523', 'n_tokens_mistral': 604, 'n_tokens_neox': 580, 'n_words': 355}