Merge branch 'feature-sliced:master' into layers-strong-rules2

Author: sanua356

LICENSE

@@ -1,6 +1,6 @@
 MIT License
 
-Copyright (c) 2018-2023 Feature-Sliced Design core-team
+Copyright (c) 2018-2025 Feature-Sliced Design core-team
 
 Permission is hereby granted, free of charge, to any person obtaining a copy
 of this software and associated documentation files (the "Software"), to deal

i18n/en/docusaurus-plugin-content-docs/current/branding.md

@@ -78,4 +78,3 @@ Work in progress...
 
 - [Discussion (github)](https://github.com/feature-sliced/documentation/discussions/399)
 - [History of development with references (figma)](https://www.figma.com/file/RPphccpoeasVB0lMpZwPVR/FSD-Brand?node-id=0%3A1)
-- [Rebranding demo](https://rebrand-sliced.netlify.app/en/)

i18n/en/docusaurus-plugin-content-docs/current/guides/tech/with-nextjs.mdx

@@ -102,7 +102,7 @@ the FSD project structure inside the `src` folder. You should still also add the
 │   ├── app            # FSD app folder
 │   ├── entities
 │   ├── features
-│   ├── pages          # FSD app folder
+│   ├── pages          # FSD pages folder
 │   ├── shared
 │   ├── widgets
 ```

i18n/en/docusaurus-plugin-content-docs/current/reference/public-api.md

@@ -29,7 +29,7 @@ export * from "./ui/Comment";  // 👎 don't try this at home
 export * from "./model/comments";  // 💩 this is bad practice
 ```
 
-This hurts the discoverability of a slice because you can't easily tell what the interface of this slice is. Not knowing the interface means that you have to dig deep into the code of a slice to understand how to integrate it. Another problem is that you might accidentally expose the module internals accidentally, which will make refactoring difficult if someone starts depending on them.
+This hurts the discoverability of a slice because you can't easily tell what the interface of this slice is. Not knowing the interface means that you have to dig deep into the code of a slice to understand how to integrate it. Another problem is that you might accidentally expose the module internals, which will make refactoring difficult if someone starts depending on them.
 
 ## Public API for cross-imports {#public-api-for-cross-imports}
 

i18n/en/docusaurus-theme-classic/footer.json

@@ -60,7 +60,7 @@
         "description": "The label of footer link with label=GitHub linking to https://github.com/feature-sliced"
     },
     "copyright": {
-        "message": "Copyright © 2018-2023  Feature-Sliced Design",
+        "message": "Copyright © 2018-2025  Feature-Sliced Design",
         "description": "The footer copyright"
     }
 }

i18n/ja/docusaurus-plugin-content-docs/current/branding.md

@@ -77,4 +77,3 @@ FSDには異なるコンテキスト用のいくつかのロゴバリエーシ
 
 - [ディスカッション (github)](https://github.com/feature-sliced/documentation/discussions/399)
 - [リブランディングの歴史と参考資料 (figma)](https://www.figma.com/file/RPphccpoeasVB0lMpZwPVR/FSD-Brand?node-id=0%3A1)
-- [リブランディングデモ](https://rebrand-sliced.netlify.app/en/)

i18n/ja/docusaurus-plugin-content-docs/current/get-started/overview.mdx

@@ -120,7 +120,7 @@ _＊ — App層とShared層のレイヤーは他のレイヤーとは異なり
 
 3. インポートのルール違反を徐々に修正しながら、エンティティやフィーチャーを抽出する。
 
-リファクタリング中に新しい大きななエンティティを追加することや、部分的なリファクタリングは避けることをお勧めします。
+リファクタリング中に新しい大きなエンティティを追加することや、部分的なリファクタリングは避けることをお勧めします。
 
 ## 次のステップ {#next-steps}
 

i18n/ja/docusaurus-theme-classic/footer.json

@@ -60,7 +60,7 @@
         "description": "The label of footer link with label=GitHub linking to https://github.com/feature-sliced"
     },
     "copyright": {
-        "message": "Copyright © 2018-2024  Feature-Sliced Design",
+        "message": "Copyright © 2018-2025  Feature-Sliced Design",
         "description": "The footer copyright"
     }
 }