diff --git a/docs/topics/advanced-usage.topic b/docs/topics/advanced-usage.topic
index 5ff80bc..9791a04 100644
--- a/docs/topics/advanced-usage.topic
+++ b/docs/topics/advanced-usage.topic
@@ -29,7 +29,7 @@
- By defending, the name of the root element is formed from the basic name of the feed class.
+ By default, the name of the root element is derived from the base name of the feed class.
@@ -44,7 +44,7 @@
- To disable the addition of the main element, specify its name as empty -
To add information to the beginning of the root element (if present) or without it,
override the
-
- If it is necessary to change the procedure for the output of the root element relative to the
+ If you need to change the order in which the root element is output relative to the
information block, set the
@@ -152,7 +152,7 @@
To insert XML fragments “as is”, use the
- By default, feeds will be stored in the
- Database queries use chunks, which are
- To apply the formatting of the code style, follow the console command:
+ To apply code style formatting, run the following console command:
null or
+ To disable the addition of the root element, specify its name as empty — null or
"".
info method in the feed class and call the creation of an object that extend the
+ info method in the feed class and create an object that extends the
DragonCode\LaravelFeed\Feeds\Info\FeedInfo class:
beforeInfo parameter in the root method:
@value field must be a string.
+ Note that the value of the @value field must be a string.
@mixed directive:
@@ -211,7 +211,7 @@
public storage,
+ By default, feeds are stored in public storage,
and the file name will be automatically generated from the feed class name after
App\Feeds\ in kebab-case format.
For example:
@@ -235,7 +235,7 @@
1000 bytes by default.
+ Database queries use chunks, which are 1000 items by default.
You can change this by overriding the chunkSize method:
-
+
@@ -35,18 +35,18 @@
- Also, this console command can create classes of the element and information along with the feed class.
- To do this, use --item and --info parameters.
+ This console command can also create the item and info classes along with the feed class.
+ To do this, use the --item and --info options.
- When creating a feed, an operation/migration will also be created to add it to the database. + When creating a feed, an operation or a migration will also be created to add it to the database.
- If the project uses the
+ If the project uses
- This is necessary to add and manage information about feeds in the database. + This is required to add and manage feed information in the database.
- Fill in the main feed class. For example: + Populate the main feed class. For example:
- Fill in the feed item class. For example: + Populate the feed item class. For example:
- As a result, all active feeds (is_active = true) will be launched from the
+ As a result, all active feeds (is_active = true) will be executed from the
feeds table (or the one you specified in the %config-filename% file).
- However, instead of being launched for execution, such feeds will be marked with the
+ However, instead of being executed, such feeds will be marked with the
SKIP status.
- This will enable you to register calls to all active feeds according to the launch schedule you specified in the
+ This will enable you to register calls to all active feeds according to the schedule you specified in the
expression column of the database.
- %config-filename% file.
Generate the feed and its item class using the following console command:
@@ -29,16 +29,16 @@Implement the feed root element, attributes, query builder, output filename, and item mapping as shown below:
- Define the XML element name and map your model properties to the corresponding sitemap tags: + Define the XML element name and map your model’s properties to the corresponding sitemap tags:
- Add a filesystem disk that points to the directory containing your sitemaps in + Add a file system disk that points to the directory containing your sitemaps in the config/filesystems.php configuration file:
- Then create the public symlink so the files are accessible in the browser: + Then create the public symlink so the files are accessible in a browser:
- A generated sitemap.xml for your products will look like this: + The generated sitemap.xml for your products will look like this: