Fixed a few more infrastructure namespaces

Author: davidbyoung

http-basics.md

@@ -43,7 +43,7 @@ use Opulence\Ioc\Bootstrappers\Bootstrapper;
 use Opulence\Ioc\IContainer;
 use Opulence\Orm\Repositories\IRepository;
 use Project\Application\Http\Controllers\UserList;
-use Project\Domain\Users\Orm\UserRepo;
+use Project\Domain\Users\UserRepo;
 
 class UserBootstrapper extends Bootstrapper
 {

orm-data-mappers.md

@@ -80,7 +80,7 @@ All data mappers must implement `Opulence\Orm\DataMappers\IDataMapper`, which in
 You'll frequently find yourself wanting to query entities by some criteria besides Id.  For example, you might want to look up posts by title using a `getByTitle()` method.  Let's create an interface with this method:
 
 ```php
-namespace Project\Domain\Posts\Orm\DataMappers;
+namespace Project\Infrastructure\Posts\DataMappers;
 
 use Opulence\Orm\DataMappers\IDataMapper;
 
@@ -410,7 +410,7 @@ Our `getByTitle()` method calls `$this->read()`, which automatically handles rea
 Instead of just containing the author's name, let's say your `Post` object contains an `Author` object.  Whenever you query a `Post` object from the data mapper, you'll also need to query the `Author` object.  The easiest way to do this is to inject the author repository into the post data mapper:
 
 ```php
-use Project\Domain\WordPress\Orm\AuthorRepo;
+use Project\Domain\WordPress\AuthorRepo;
 use Project\Domain\WordPress\Post;
 
 class PostDataMapper extends SqlDataMapper

orm-repositories.md

@@ -92,7 +92,7 @@ As you can see, there is no `save()` method in repositories.  To actually save a
 use Opulence\Orm\Repositories\Repository;
 use Opulence\Orm\UnitOfWork;
 use Project\Domain\WordPress\Post;
-use Project\Infrastructure\WordPress\Orm\DataMappers\PostSqlDataMapper;
+use Project\Infrastructure\WordPress\DataMappers\PostSqlDataMapper;
 
 // Assume $unitOfWork is already instantiated
 $repo = new Repository(Post::class, new PostSqlDataMapper(), $unitOfWork);