Spelling_and_grammer_mistakes (#854)

Co-authored-by: Victor Villar <59838221+vvilpas@users.noreply.github.com>

.pylintrc

@@ -43,7 +43,7 @@ extension-pkg-whitelist=
 confidence=
 
 # Enable the message, report, category or checker with the given id(s). You can
-# either give multiple identifier separated by comma (,) or put this option
+# either give multiple identifiers separated by comma (,) or put this option
 # multiple time (only on the command line, not in the configuration file where
 # it should appear only once). See also the "--disable" option for examples.
 #enable=
@@ -70,7 +70,7 @@ disable=no-self-use,        # disabled as it is too verbose
     unnecessary-pass,   # allow for methods with just "pass", for clarity
     no-else-return,     # relax "elif" after a clause with a return
     docstring-first-line-empty, # relax docstring style
-    unsubscriptable-object # pylint can't determin this for numpy types
+    unsubscriptable-object # pylint can't determine this for numpy types
 
 
 

.travis.yml

@@ -17,7 +17,7 @@ sudo: false
 ###############################################################################
 
 # These are used for avoiding repeating code, and due to problems with
-# overriding some keys (in particular, "os" and "language: ptyhon") when using
+# overriding some keys (in particular, "os" and "language: python") when using
 # the standard travis matrix with stages.
 #
 # This allows re-using different "sets" of configurations in the stages

BENCHMARKING.md

@@ -11,7 +11,7 @@ There you'll find a bunch of `*_benchmarks.py` files which represent the differe
 
 
 # How to run the benchmarks
-All prerequistes for building the project need to be installed in the system, take a look at the [CONTRIBUTING guide](.github/CONTRIBUTING.md) if you don't have them already installed.
+All prerequisites for building the project need to be installed in the system, take a look at the [CONTRIBUTING guide](.github/CONTRIBUTING.md) if you don't have them already installed.
 
 Install Airspeed Velocity (`ASV`):
 ```
@@ -23,7 +23,7 @@ Move to the `test` directory:
 $ cd test
 ```
 
-And run `asv` using the correct configuration file, depeding on what O.S. you are executing them:
+And run `asv` using the correct configuration file, depending on what O.S. you are executing them:
 Linux:
 ```
 $ asv run --config asv.linux.conf.json
@@ -41,7 +41,7 @@ After the completion of the tests, you will see the results with a format simila
 ```
 · Creating environments
 · Discovering benchmarks
-· Running 3 total benchmarks (1 commits * 1 environments * 3 benchmarks)
+· Running 3 total benchmarks (1 commit * 1 environment * 3 benchmarks)
 [  0.00%] · For qiskit-aer commit 8b4f4de1 <master>:
 [  0.00%] ·· Benchmarking conda-py3.7
 [ 16.67%] ··· Running (quantum_volume_benchmarks.QuantumVolumeTimeSuite.time_quantum_volume--)..
@@ -83,7 +83,7 @@ After the completion of the tests, you will see the results with a format simila
 
 # Interpreting the data
 
-The output format is pretty self-explanatory, so every row starting with the text: `Num. quits:` repesents all the benchmarks run for this number of quibits configuration, more precisely, we run 4 benchmarks for every number of qubits configuration, and each of the benchmarks are run with a different noise model, so for example, this line:
+The output format is pretty self-explanatory, so every row starting with the text: `Num. quits:` represents all the benchmarks run for this number of qubits configuration, more precisely, we run 4 benchmarks for every number of qubits configuration, and each of the benchmarks are run with a different noise model, so for example, this line:
 ```
   Quantum Volume   No Noise   Mixed Unitary Noise   Reset Noise   Kraus Noise
 ================= ========== ===================== ============= =============

CMakeLists.txt

@@ -1,7 +1,7 @@
 # CMake config file to build AER
 #
 # For Linux and Mac, we can build both statically or dynamically. The latter is
-# the default. If you want to build an static executable/library, you need to set
+# the default. If you want to build a static executable/library, you need to set
 # STATIC_LINKING to True, example:
 #     out$ cmake -DSTATIC_LINKING=True ..
 #
@@ -19,7 +19,7 @@ if(NOT DEFINED AER_BLAS_LIB_PATH AND DEFINED ENV{AER_BLAS_LIB_PATH})
 	set(AER_BLAS_LIB_PATH $ENV{AER_BLAS_LIB_PATH})
 endif()
 
-# Warning: Because of a bug on CMake's FindBLAS or (it's not clear whoes fault is)
+# Warning: Because of a bug on CMake's FindBLAS or (it's not clear who's fault is)
 # libopenblas.a for Ubuntu (maybe others) we need to copy the file:
 # cmake/FindBLAS.cmake.fix-static-linking, to the directory were CMake Modules are
 # installed in the system, but with the name: FindBLAS.cmake

CODE_OF_CONDUCT.md

@@ -2,7 +2,7 @@
 
 ## 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, gender identity and expression, level of experience, nationality, personal appearance, race, religion, or sexual identity and orientation.
+In the interest of fostering an open and welcoming environment, we as contributors and maintainers pledge to make participation in our project and our community a harassment-free experience for everyone, regardless of age, body size, disability, ethnicity, gender identity and expression, level of experience, nationality, personal appearance, race, religion, or sexual identity and orientation.
 
 ## Our Standards
 

CONTRIBUTING.md

@@ -58,7 +58,7 @@ is that if your code contribution has user facing changes that you will write
 the release documentation for these changes. This documentation must explain
 what was changed, why it was changed, and how users can either use or adapt
 to the change. The idea behind release documentation is that when a naive
-user with limited internal knowledege of the project is upgrading from the
+user with limited internal knowledge of the project is upgrading from the
 previous release to the new one, they should be able to read the release notes,
 understand if they need to update their program which uses qiskit, and how they
 would go about doing that. It ideally should explain why they need to make
@@ -681,7 +681,7 @@ These are the flags:
 
 * AER_CUDA_ARCH
 
-    This flag allows us we to specify the CUDA architecture instead of letting the build systemm auto detect it.
+    This flag allows us we to specify the CUDA architecture instead of letting the build system auto detect it.
     It can also be set as an ENV variable with the same name, although the flag takes precedence.
     
     Values:  Auto | Common | All | List of valid CUDA architecture(s).
@@ -709,7 +709,7 @@ The integration tests for Qiskit python extension are included in: `test/terra`.
 
 ## Platform support
 
-Bare in mind that every new feature/change needs to be compatible with all our
+Bear in mind that every new feature/change needs to be compatible with all our
 supported platforms: Win64, MacOS (API Level >= 19) and Linux-x86_64. The
 Continuous Integration (CI) systems will run builds and pass all the
 corresponding tests to verify this compatibility.