Merge pull request #1260 from sinapis-amicus/master

correct spelling errors & typos

Author: dromer

CONTRIBUTING.md

@@ -12,8 +12,8 @@ Guidelines:
  * Report your __browser type and version__, any __JavaScript errors in the console__ and any other details like __server operating system__, __php version__, __SQL Server type and version__ etc.
 * Check your logs, especially your __Web Server Log__ as well as __app/logs/partkeepr.log__
 * Only attach the parts of the logs which are __relevant__ to the problem.
-* Make sure the problem is __reproducable__. If it only happened one time, you have to find out on how to reproduce it.
-* Explain, in simple words, __when__ the issue occured. For example: Don't write "I can't create a part". Rather write: "I clicked on Add Part, entered a Part Name, then I clicked the save button, then nothing happens. There were no JavaScript errors in the console, and no HTTP Request was sent."
+* Make sure the problem is __reproducible__. If it only happened one time, you have to find out on how to reproduce it.
+* Explain, in simple words, __when__ the issue occurred. For example: Don't write "I can't create a part". Rather write: "I clicked on Add Part, entered a Part Name, then I clicked the save button, then nothing happens. There were no JavaScript errors in the console, and no HTTP Request was sent."
 * Try to limit your bug report to only __essential__ steps on how to reproduce the issue.
 * In short, help the volunteers maintaining the project to spend as little effort as possible on the issue, so that we can have more time adding features and fixing bugs more easily.
 

app/PartKeeprRequirements.php

@@ -24,7 +24,7 @@ function_exists('imagecreate'),
         $this->addRequirement(
             function_exists('imagettftext'),
             sprintf('GD library has no FreeType support'),
-            sprintf('Install the FreeType extension and make sure GD extention can use it')
+            sprintf('Install the FreeType extension and make sure GD extension can use it')
         );
 
         $this->addRequirement(

app/config/parameters.php.dist

@@ -96,7 +96,7 @@ $container->setParameter('fr3d_ldap.driver.username', null);
 // The password to use for LDAP queries
 $container->setParameter('fr3d_ldap.driver.password', null);
 
-// true to require a DN for binding attemts, false otherwise
+// true to require a DN for binding attempts, false otherwise
 $container->setParameter('fr3d_ldap.driver.bindRequiresDn', false);
 
 // The base DN to query for users

docker/README.md

@@ -19,7 +19,7 @@ This image is not ready to run but serves as a basis for the other images relate
 
 The docker-compose file registers multiple container services. The main PartKeepr application is called `app`. The database is a basic configuration with `mariadb:10.1` for compatibility. Third, there is a service called `initdb`. Its purpose is to restore the database and `data` folder to a pristine state. This one should normally not be used unless one wants to reset the database.
 
-**Note:** There needs to be a useful default inserted into the initdb. At the moment it only clears out the database to be valid but containing no parts at all. Exactly the situtation you have after a fresh installation. Some test data might be useful here.
+**Note:** There needs to be a useful default inserted into the initdb. At the moment it only clears out the database to be valid but containing no parts at all. Exactly the situation you have after a fresh installation. Some test data might be useful here.
 
 ## The main development image
 
@@ -54,13 +54,13 @@ This guide assumes, you have just freshly checked out the PartKeer repository fr
 - Call `docker-compose pull` to fetch all images from the docker hub. Alternatively you could [build the images manually](#building-the-images-manually).
 - Now you need to fire up the database and let it initialize. This is done by callng `docker-compose up -d db`. You can peek into the process by `docker-compose logs -f db`. Wait for a message that the server is ready for connections and listening on port 3306. Using `<Ctrl><c>`, you can exit from the logs.
 - Build the `initdb` image by calling `docker-compose build initdb`. This will take a few moments as it builds a docker image.
-  By default the line `RESET_DATABASE: 'yes'` in the file `docker-compose.yml` is commented. This is to avoid accidentially removing your data. Uncomment the line. Then:
+  By default the line `RESET_DATABASE: 'yes'` in the file `docker-compose.yml` is commented. This is to avoid accidentally removing your data. Uncomment the line. Then:
   - Initialize the data by calling `docker-compose up initdb`.
   - Recomment the line in the `docker-compose.yml` file you just uncommented.
 - Now, you can fire up the main container by calling `docker-compose up -d app`.
 - The container will initialize some dependencies. This might take some time as well. Again using `docker-compose logs -f app` you can peek into the process and with `<Ctrl><c>` you can return to the console.
    There might be some error messages regarding missing tables.
-- The partkeepr instance is avaliable at http://127.0.0.1:8082/.
+- The partkeepr instance is available at http://127.0.0.1:8082/.
   - Note: If you don't set `PARTKEEPR_FORCE_UPDATE` to `yes` in the `docker-compose` file on your first run you will get a white screen as you need to start the [setup](http://127.0.0.1:8082/setup/) once. Just accept the defaults but do not create a new set of users (keep the existing ones) and select HTTP Basic authentication.
 - You may or may or not want to set up a cron job as described. The check is disabled by default.
   - Alternatively, you can run the cron command manually with `php app/console partkeepr:cron:run` after logging in to the container with `docker exec -it partkeepr_dev_app_1 bash`.

docker/development/app/user-entrypoint.sh

@@ -4,7 +4,7 @@ cd /var/www/pk
 
 # Check if parameters are present
 if [ ! -f app/config/parameters.php ]; then
-	echo 'No configuration was found yet. A defult configuration was generated.' >&2
+	echo 'No configuration was found yet. A default configuration was generated.' >&2
 	echo 'Please visit the setup page if you encounter issues.' >&2
 
 	# Remove any db related config from the dist file

src/PartKeepr/AuthBundle/Services/UserService.php

@@ -96,7 +96,7 @@ public function getProviderTypeByClass($providerClass)
     }
 
     /**
-     * Syncronizes the data of the given user with the FOSRestBundle.
+     * Synchronizes the data of the given user with the FOSRestBundle.
      *
      *
      * @param $user

src/PartKeepr/CoreBundle/Services/SystemService.php

@@ -113,7 +113,7 @@ public function getSystemInformation()
     /**
      * Returns the database schema status.
      *
-     * This method is usuall called once the user logs in, and alerts him if the schema is not up-to-date.
+     * This method is usually called once the user logs in, and alerts him if the schema is not up-to-date.
      *
      * Returns either status incomplete if the schema is not up-to-date, or complete if everything is OK.
      */

src/PartKeepr/FrontendBundle/Resources/public/js/Components/ModelTreeMaker/ModelTreeMaker.js

@@ -38,7 +38,7 @@ Ext.define("PartKeepr.ModelTreeMaker.ModelTreeMaker", {
      * @param {Ext.data.NodeInterface} node The current node
      * @param {Ext.data.Model} model The model
      * @param {String} prefix The prefix. Omit if first called
-     * @param {Function} callback The calback, optional
+     * @param {Function} callback The callback, optional
      */
     make: function (node, model, prefix, callback)
     {

src/PartKeepr/FrontendBundle/Resources/public/js/Components/StorageLocation/StorageLocationMultiAddWindow.js

@@ -82,7 +82,7 @@ Ext.define("PartKeepr.StorageLocationMultiCreateWindow", {
         this.addButton.enable();
 
         if (response.data.length > 0) {
-            Ext.Msg.alert(i18n("Errors occured"), implode("<br>", response.data));
+            Ext.Msg.alert(i18n("Errors occurred"), implode("<br>", response.data));
         } else {
             this.close();
         }

src/PartKeepr/FrontendBundle/Resources/public/js/Components/Widgets/EntityQueryPanel.js

@@ -254,8 +254,8 @@ Ext.define("PartKeepr.Widgets.EntityQueryPanel", {
 
     },
     /**
-     * Syncronizes the internal columns storage with the grid. The reason it is done that way is because we can't
-     * operate on the return value of getColumns() directly, as these are instanciated objects which get removed
+     * Synchronizes the internal columns storage with the grid. The reason it is done that way is because we can't
+     * operate on the return value of getColumns() directly, as these are instantiated objects which get removed
      * during a reconfigure operation.
      */
     syncColumns: function ()