Update glossary

CODE-OF-CONDUCT.md

@@ -0,0 +1,53 @@
+Qiita's Code of Conduct
+=======================
+
+Our Pledge
+----------
+
+In the interest of fostering an open and welcoming environment, we as contributors and maintainers pledge to making participation in our project and our community a harassment-free experience for everyone, regardless of age, body size, disability, ethnicity, sex characteristics, gender identity and expression, level of experience, education, socio-economic status, nationality, personal appearance, race, religion, or sexual identity and orientation.
+
+Our Standards
+-------------
+
+Examples of behavior that contributes to creating a positive environment include:
+
+* Using welcoming and inclusive language
+* Being respectful of differing viewpoints and experiences
+* Gracefully accepting constructive criticism
+* Focusing on what is best for the community
+* Showing empathy towards other community members
+
+Examples of unacceptable behavior by participants include:
+
+* The use of sexualized language or imagery and unwelcome sexual attention or advances
+* Trolling, insulting/derogatory comments, and personal or political attacks
+* Public or private harassment
+* Publishing others’ private information, such as a physical or electronic address, without explicit permission
+* Other conduct which could reasonably be considered inappropriate in a professional setting
+
+
+Our Responsibilities
+--------------------
+
+Project maintainers are responsible for clarifying the standards of acceptable behavior and are expected to take appropriate and fair corrective action in response to any instances of unacceptable behavior.
+
+Project maintainers have the right and responsibility to remove, edit, or reject comments, commits, code, issues, and other contributions that are not aligned to this Code of Conduct, or to ban temporarily or permanently any contributor for other behaviors that they deem inappropriate, threatening, offensive, or harmful.
+
+Scope
+-----
+
+This Code of Conduct applies within all project spaces, and it also applies when an individual is representing the project or its community in public spaces. Examples of representing a project or community include using an official project e-mail address, posting via an official social media account, or acting as an appointed representative at an online or offline event. Representation of a project may be further defined and clarified by project maintainers.
+
+Enforcement
+-----------
+
+Instances of abusive, harassing, or otherwise unacceptable behavior may be reported by contacting the project team at qiita.help@gmail.com. All complaints will be reviewed and investigated and will result in a response that is deemed necessary and appropriate to the circumstances. The project team is obligated to maintain confidentiality with regard to the reporter of an incident. Further details of specific enforcement policies may be posted separately.
+
+Project maintainers who do not follow or enforce the Code of Conduct in good faith may face temporary or permanent repercussions as determined by other members of the project’s leadership.
+
+Attribution
+-----------
+
+[This Code of Conduct is adapted from the Contributor Covenant, version 1.4](https://www.contributor-covenant.org/version/1/4/code-of-conduct.html).
+
+For answers to common questions about this code of conduct, see https://www.contributor-covenant.org/faq

README.rst

@@ -10,9 +10,9 @@ These new technologies are generating vast amounts of data, even from a single
 study or sample, leading to challenges in storage, representation, analysis,
 and integration of the disparate data types. Qiita was designed to allow users
 address these new challenges by keeping track of multiple studies with multiple
-‘omics data. Additionally, Qiita is capable of supporting multiple analytical
+'omics data. Additionally, Qiita is capable of supporting multiple analytical
 pipelines through a 3rd-party plugin system, allowing the user to have a single
-entry point for all their analyses. Qiita’s main site provides database and
+entry point for all their analyses. Qiita's main site provides database and
 compute resources to the global community, alleviating the technical burdens,
 such as familiarity with the command line or access to compute power, that are
 typically limiting for researchers studying microbial ecology.
@@ -76,7 +76,7 @@ future.
 * Creation of a REST API to query and access the data hosted by Qiita.
 * Improved analysis pipeline for target gene datasets.
 * Crowd-sourced metadata curation of existing studies: improve the metadata of
-  existing studies by submitting “fix proposals” to the authors of the study.
+  existing studies by submitting a fix proposals to the authors of the study.
 
 
 .. |Build Status| image:: https://travis-ci.org/biocore/qiita.png?branch=master

qiita_pet/support_files/doc/source/faq.rst

@@ -118,6 +118,18 @@ To update your unzip for most operating systems you can simply use your regular
 admin program. However, for Mac we suggest using
 `this version of unzip <ftp://ftp.microbio.me/pub/qiita/unzip>`__.
 
+Additionally, there is a chance that you will see an error/warning message like this:
+``extracting: BIOM/57457/all.biom bad CRC f6b2a86b (should be 38903659)``. These
+messages are consequence of the zip library we are using internally and are fine to
+ignore. If you want to check them, we suggest taking any of the files and generating their
+CRC32 checksum; in MAC's you can run ``crc32 [filename]`` and should get the first number
+in that message; for example:
+
+.. code-block:: bash
+
+   $ crc32 57457_all.biom
+   f6b2a86b
+
 Do you have general analytical questions?
 -----------------------------------------