chore(errors): rename folders to match namespaces

3 files changed, 0 insertions, 34 deletions

diff --git a/docs/content/error/location/ihshprfx.ngdoc b/docs/content/error/location/ihshprfx.ngdoc
deleted file mode 100644
index 8acab933..00000000
--- a/docs/content/error/location/ihshprfx.ngdoc
+++ /dev/null
@@ -1,17 +0,0 @@
-@ngdoc error
-@name $location:ihshprfx
-@fullName Missing Hash Prefix
-@description
-
-This error occurs when {@link ng.$location $location} service is configured to use a hash prefix but this prefix was not present in a url that the `$location` service was asked to parse.
-
-For example if you configure `$location` service with prefix `'!'`:
-```
-myApp.config(function($locationProvider) {
-  $locationProvider.prefix('!');
-});
-```
-
-If you enter the app at url `http:/myapp.com/#/myView` this error will be throw.
-
-The correct url for this configuration is `http:/myapp.com/#!/myView` (note the `'!'` after `'#'` symbol).
diff --git a/docs/content/error/location/ipthprfx.ngdoc b/docs/content/error/location/ipthprfx.ngdoc
deleted file mode 100644
index 55b75d86..00000000
--- a/docs/content/error/location/ipthprfx.ngdoc
+++ /dev/null
@@ -1,8 +0,0 @@
-@ngdoc error
-@name $location:ipthprfx
-@fullName Invalid or Missing Path Prefix
-@description
-
-This error occurs when you configure the {@link ng.$location `$location`} service in the html5 mode, specify a base url for your application via `<base>` element and try to update the location with a path that doesn't match the base prefix.
-
-To resolve this issue, please check the base url specified via the `<base>` tag in the head of your main html document, as well as the url that you tried to set the location to.
diff --git a/docs/content/error/location/isrcharg.ngdoc b/docs/content/error/location/isrcharg.ngdoc
deleted file mode 100644
index 4b60ddd5..00000000
--- a/docs/content/error/location/isrcharg.ngdoc
+++ /dev/null
@@ -1,9 +0,0 @@
-@ngdoc error
-@name $location:isrcharg
-@fullName Wrong $location.search() argument type
-@description
-
-To resolve this error, ensure that the first argument for the `$location.search` call is a `string` or an object.
-You can use the stack trace associated with this error to identify the call site that caused this issue.
-
-To learn more, please consult the {@link ng.$location `$location`} api docs.