From dbb5d0bc62e11ed5a02bb5427685bc376d30b768 Mon Sep 17 00:00:00 2001 From: Dan Harrin Date: Thu, 31 Aug 2023 13:20:50 +0300 Subject: [PATCH] wip --- packages/actions/docs/10-upgrade-guide.md | 2 +- packages/forms/docs/10-upgrade-guide.md | 2 +- packages/notifications/docs/07-upgrade-guide.md | 2 +- packages/panels/docs/14-upgrade-guide.md | 2 +- packages/tables/docs/13-upgrade-guide.md | 2 +- 5 files changed, 5 insertions(+), 5 deletions(-) diff --git a/packages/actions/docs/10-upgrade-guide.md b/packages/actions/docs/10-upgrade-guide.md index fa3eace5cd..ee79763898 100644 --- a/packages/actions/docs/10-upgrade-guide.md +++ b/packages/actions/docs/10-upgrade-guide.md @@ -34,7 +34,7 @@ You can now `composer remove filament/upgrade` as you don't need it anymore. ## Upgrading manually -After upgrading the dependency via Composer, you should execute `php artisan filament:upgrade` in order to clear any caches and publish the new assets. +After upgrading the dependency via Composer, you should execute `php artisan filament:upgrade` in order to clear any Laravel caches and publish the new frontend assets. ### Low-impact changes diff --git a/packages/forms/docs/10-upgrade-guide.md b/packages/forms/docs/10-upgrade-guide.md index 3a600bc25f..cde1d584bb 100644 --- a/packages/forms/docs/10-upgrade-guide.md +++ b/packages/forms/docs/10-upgrade-guide.md @@ -33,7 +33,7 @@ You can now `composer remove filament/upgrade` as you don't need it anymore. ## Upgrading manually -After upgrading the dependency via Composer, you should execute `php artisan filament:upgrade` in order to clear any caches and publish the new assets. +After upgrading the dependency via Composer, you should execute `php artisan filament:upgrade` in order to clear any Laravel caches and publish the new frontend assets. ### High-impact changes diff --git a/packages/notifications/docs/07-upgrade-guide.md b/packages/notifications/docs/07-upgrade-guide.md index f26e6ce450..d763931771 100644 --- a/packages/notifications/docs/07-upgrade-guide.md +++ b/packages/notifications/docs/07-upgrade-guide.md @@ -33,7 +33,7 @@ You can now `composer remove filament/upgrade` as you don't need it anymore. ## Upgrading manually -After upgrading the dependency via Composer, you should execute `php artisan filament:upgrade` in order to clear any caches and publish the new assets. +After upgrading the dependency via Composer, you should execute `php artisan filament:upgrade` in order to clear any Laravel caches and publish the new frontend assets. ### High-impact changes diff --git a/packages/panels/docs/14-upgrade-guide.md b/packages/panels/docs/14-upgrade-guide.md index 28f8d842ba..6ae5ec5c31 100644 --- a/packages/panels/docs/14-upgrade-guide.md +++ b/packages/panels/docs/14-upgrade-guide.md @@ -36,7 +36,7 @@ You can now `composer remove filament/upgrade` as you don't need it anymore. ## Upgrading manually -After upgrading the dependency via Composer, you should execute `php artisan filament:upgrade` in order to clear any caches and publish the new assets. +After upgrading the dependency via Composer, you should execute `php artisan filament:upgrade` in order to clear any Laravel caches and publish the new frontend assets. ### High-impact changes diff --git a/packages/tables/docs/13-upgrade-guide.md b/packages/tables/docs/13-upgrade-guide.md index 8fcfa197a2..244ff15ba9 100644 --- a/packages/tables/docs/13-upgrade-guide.md +++ b/packages/tables/docs/13-upgrade-guide.md @@ -33,7 +33,7 @@ You can now `composer remove filament/upgrade` as you don't need it anymore. ## Upgrading manually -After upgrading the dependency via Composer, you should execute `php artisan filament:upgrade` in order to clear any caches and publish the new assets. +After upgrading the dependency via Composer, you should execute `php artisan filament:upgrade` in order to clear any Laravel caches and publish the new frontend assets. ### High-impact changes