- Fix namespace

- Extend the README

Author: vixducis

README.md

@@ -1,14 +1,24 @@
 # Informat API Wrapper
 PHP client library for the Informat school software API. This client allows you to 
 - Fetch students
-- Fetch registration
+- Fetch registrations
 - Create new preregistrations
 
+## Installation
+You can simply install the library through composer:
+```
+composer require koba/informat-php-client
+```
+The library also requires a PSR-17 and PSR-18 implementation. If these are not yet included in your project, you can install Guzzle 7 to meet this requirement (although any other implementation will work fine):
+```
+composer require guzzlehttp/guzzle
+```
+
 ## Usage
 The library is built on 3 main 'layers':
 - The `Informat` class, which is instantiated with your client ID and secret.
-- Directories, which are logical groups of api calls. These can be obtained by function calls on the `Informat` class.
-- API calls, these can be instantiated by function calls on the directories.
+- Directories, which are logical groups of api calls. These can be obtained by using the provided methods on the `Informat` class.
+- API calls, these can be instantiated by using the provided methods on the directories.
 
 The code below is a quick example of how you can fetch students
 ```php
@@ -29,15 +39,15 @@ $informat = new Informat(
 This will return an array of `Student` objects, which has typed (and documented) properties.
 
 ### Scopes
-Creating the `Informat` object can be done fairly easily as demonstrated above. The scopes paramete might need some extra explanation.
+Creating the `Informat` object can be done fairly easily as demonstrated above. The scopes parameter might need some extra explanation.
 
 In the example above you see we pass an `AllScopesStrategy` object to the constructor. This is a way to let the API client know which scopes we want to request, which directly impacts which API calls you will be authorized to execute. The library supplies the `AllScopesStrategy`, which will request all possible scopes and the `SpecificScopesStrategy`, which allows you to specify the scopes that will be requested. Both require you to pass the institute numbers for all schools you wnat to access as parameters. The latter might be desirable if your client isn't authorized for all scopes or you want to limit the functionality for security reasons.
 
 You can also create your own scope strategy by implementing the `ScopeStrategyInterface`.
 
 ### Calls
 There are a couple of 'rules' that should be followed when managing calls
-- When creating a call using a function on a directory, all required parameters for the API call need to be passed to the function. The institute number will always be the first parameter as it is required for all API calls.
+- When creating a call using a method on a directory, all required parameters for the API call need to be passed to the function. The institute number will always be the first parameter as it is required for all API calls.
 - All optional paremeters can be set using setters on the API call.
 - Setters on the API calls returns the call itself, which means you can easily chain them together.
 - An API call will always be executed with the `send` method.
@@ -55,4 +65,4 @@ $informat
 ```
 
 ### Advanced
-The `Informat` object has some advanced setup options. You can pass an `AccessTokenManagerInterface` object, which allows you to implement your own access token caching solution. The rest of the constructor can be used to pass a [psr-18](https://www.php-fig.org/psr/psr-18/) client interface and [psr-17](https://www.php-fig.org/psr/psr-17/) HTTP response factories. If these options are omitted, the library will autodiscover any suitable implementations. If your project doesn't currently have one, you could take a look at [Guzzle 7](https://docs.guzzlephp.org/en/stable/).
+The `Informat` object has some advanced setup options. You can pass an `AccessTokenManagerInterface` object, which allows you to implement your own access token caching solution. The rest of the constructor can be used to pass a [psr-18](https://www.php-fig.org/psr/psr-18/) client interface and [psr-17](https://www.php-fig.org/psr/psr-17/) HTTP response factories. If these options are omitted, the library will autodiscover any suitable implementations.

src/Informat/Directories/Preregistrations/DeletePreregistration/DeletePreregistrationCall.php

@@ -1,6 +1,6 @@
 <?php
 
-namespace Koba\Informat\Directories\Preregistrations;
+namespace Koba\Informat\Directories\Preregistrations\DeletePreregistration;
 
 use Koba\Informat\Call\CallInterface;
 use Koba\Informat\Call\CallProcessor;