chore(errors): rename folders to match namespaces

2 files changed, 0 insertions, 91 deletions

diff --git a/docs/content/error/rootScope/infdig.ngdoc b/docs/content/error/rootScope/infdig.ngdoc
deleted file mode 100644
index e36f1d69..00000000
--- a/docs/content/error/rootScope/infdig.ngdoc
+++ /dev/null
@@ -1,17 +0,0 @@
-@ngdoc error
-@name $rootScope:infdig
-@fullName Infinite $digest Loop
-@description
-
-This error occurs when the application's model becomes unstable and each `$digest` cycle triggers a state change and subsequent `$digest` cycle.
-Angular detects this situation and prevents an infinite loop from causing the browser to become unresponsive.
-
-For example, the situation can occur by setting up a watch on a path and subsequently updating the same path when the value changes.
-
-```
-$scope.$watch('foo', function() {
-  $scope.foo = $scope.foo + 1;
-});
-```
-
-The maximum number of allowed iterations of the `$digest` cycle is controlled via TTL setting which can be configured via {@link ng.$rootScopeProvider $rootScopeProvider}.
diff --git a/docs/content/error/rootScope/inprog.ngdoc b/docs/content/error/rootScope/inprog.ngdoc
deleted file mode 100644
index 375f8fe8..00000000
--- a/docs/content/error/rootScope/inprog.ngdoc
+++ /dev/null
@@ -1,74 +0,0 @@
-@ngdoc error
-@name $rootScope:inprog
-@fullName Action Already In Progress
-@description
-
-At any point in time there can be only one `$digest` or $apply operation in progress.
-The stack trace of this error allows you to trace the origin of the currently executing $apply or $digest call.
-
-`$digest` or `$apply` are processing operational states of the Scope - data-structure in Angular that provides context for models and enables model mutation observation.
-
-Trying to reenter a `$digest` or `$apply` while one of them is already in progress is typically a sign of programming error that needs to be fixed.
-
-This error is often seen when interacting with an API that is sometimes sync and sometimes async.
-
-For example:
-
-```
-function MyController() {
-  thirdPartyComponent.getData(function(someData) {
-    scope.$apply(function() {
-      scope.someData = someData;
-    });
-  });
-}
-```
-
-The controller constructor is always instantiated from within an $apply cycle, so if the third-party component called our callback synchronously, we'd be trying to enter the $apply again.
-
-To resolve this type of issue, either fix the api to be always synchronous or asynchronous or wrap the call to the api with setTimeout call to make it always asynchronous.
-
-
-Other situation that leads to this error is when you are trying to reuse a function to by using it as a callback for code that is called by various apis inside and outside of $apply.
-
-For example:
-
-```
-myApp.directive('myDirective', function() {
-  return {
-    link: function($scope, $element) {
-      function doSomeWork() {
-        $scope.$apply(function() {
-           // do work here, and update the model
-        };
-      }
-
-      $element.on('click', doSomeWork);
-      doSomeWork(); // << this will throw an exception because templates are compiled within $apply
-    }
-  }
-});
-
-```
-
-The fix for the example above looks like this:
-```
-myApp.directive('myDirective', function() {
-  return {
-    link: function($scope, $element) {
-      function doSomeWork() {
-           // do work here, and update the model
-      }
-
-      $element.on('click', function() {
-        $scope.$apply(doSomeWork); // <<< the $apply call was moved to the callsite that doesn't execute in $apply call already
-      });
-
-      doSomeWork();
-    }
-  }
-});
-
-```
-
-To learn more about Angular processing model please check out the {@link guide/concepts concepts doc} as well as the {@link ng.$rootScope.Scope api} doc.