When the results of a query are displayed on a page, they are often split in to 'pages'*. This ensures that the server does not get overwhelmed creating one massive page, and makes things more manageable for the user.
To allow the user to see further results, the system can automatically create paging controls.
To do this, on the Query Embed dialog, select the number of items to be shown in each page (default is 10, maximum 999), and select the position where you want the paging controls to be shown.
Note: If the items are quite deep, you may want to have the paging controls appear both above and below the query results, so the user does not have to scroll to find them.
* Pages vs pages. The history of web development has, unfortunately, given us a naming collision here. A website is made up of pages - web-pages. A set of results can be split up so you don't see all of them at once - they are divided into pages. When we use the verb 'paging' we are normally talking about paging through the a view's results-set a few at a time ('a few' being the specified page size) - but, from the website's perspective, all these pages are shown on the same web-page (using different query-string parameters to let it know which part of the results set to show)